Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Infinispan to 10.0.0.Final #5295

Merged
merged 1 commit into from
Nov 7, 2019

Conversation

wburns
Copy link
Member

@wburns wburns commented Nov 7, 2019

No description provided.

@wburns wburns added the area/infinispan Infinispan label Nov 7, 2019
@wburns wburns requested a review from Sanne November 7, 2019 15:52
@@ -76,6 +80,24 @@
<type>test-jar</type>
<scope>test</scope>
</dependency>

<!-- We override these to satisfy Infinispan server -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that it won't work with 2.9.10.20191020? IMHO the BOM should be updated to Jackson 2.10.0 first

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that Infinispan Server uses a new version of Jackson that isn't compatible with the version Quarkus is currently using. The Server is only started to test the client, so this doesn't affect any Quarkus code.

Copy link
Contributor

@gastaldi gastaldi Nov 7, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But doesn't that mean that in these tests the client will use Jackson 2.10.0 too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests don't use anything that requires Jackson to be loaded afaik.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least it doesn't fail 🤷‍♂

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good question.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, is the Infinispan client using Jackson at all? I guess if it's only used in the server, then it's ok.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Infinispan Client does not use Jackson at all, it is all hotrod. I am only overriding the Jackson version for the Infinispan Server (which does use Jackson for REST), so that the client can actually talk to something.

I was referring to whether or not the Quarkus web layer used Jackson, maybe it only uses it for non String types? All my return types are String in the test.

Sanne
Sanne previously approved these changes Nov 7, 2019
@Sanne Sanne dismissed their stale review November 7, 2019 16:19

failed ci

@Sanne Sanne self-requested a review November 7, 2019 16:19
Copy link
Member

@Sanne Sanne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This failure seems legit, and will need to be fixed:

[WARNING] 
Dependency convergence error for org.eclipse.microprofile.metrics:microprofile-metrics-api:2.0.2 paths to dependency are:
+-io.quarkus:quarkus-infinispan-embedded:999-SNAPSHOT
  +-org.infinispan:infinispan-core:10.0.0.Final
    +-org.eclipse.microprofile.metrics:microprofile-metrics-api:2.0.2
and
+-io.quarkus:quarkus-infinispan-embedded:999-SNAPSHOT
  +-org.infinispan:infinispan-core:10.0.0.Final
    +-io.smallrye:smallrye-metrics:2.3.0
      +-org.eclipse.microprofile.metrics:microprofile-metrics-api:2.2

[WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Failed while enforcing releasability. See above detailed error message.
[INFO] ------------------------------------------------------------------------

@wburns wburns force-pushed the update_infinispan_10.0.0.Final branch from fec8216 to c46892e Compare November 7, 2019 17:31
@wburns
Copy link
Member Author

wburns commented Nov 7, 2019

Updated, should be fixed now :)

@Sanne Sanne self-requested a review November 7, 2019 18:20
Copy link
Member

@Sanne Sanne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! Tested it with native images locally as well. I'll wait for CI, then merge.

@Sanne Sanne added this to the 1.1.0 milestone Nov 7, 2019
@Sanne Sanne added the backport? label Nov 7, 2019
@wburns
Copy link
Member Author

wburns commented Nov 7, 2019

@Sanne so to backport do I just cherry pick into the 1.0 branch? I haven't been keeping up with how you guys have been doing release dev.

@Sanne
Copy link
Member

Sanne commented Nov 7, 2019

@wburns we target the next release (1.1) and add a label "backport" to have it considered for the 1.0.0.Final gatekeepers. It's just a hint for them though, risk assesment will decide..

@wburns
Copy link
Member Author

wburns commented Nov 7, 2019

Okay, so nothing more on my side once this is integrated, thanks.

@wburns
Copy link
Member Author

wburns commented Nov 7, 2019

I will say I would love for this to be backported to 1.0 though 😀

@gastaldi gastaldi merged commit dea88a8 into quarkusio:master Nov 7, 2019
@@ -11,7 +11,7 @@

<artifactId>quarkus-infinispan-embedded</artifactId>
<name>Quarkus - Infinispan - Embedded - Runtime</name>
<description>Run an embedded Infinispan data grid server for distributed caching</description>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit late to the party but isn't this going to be a problem with code.quarkus.io once we make this extension public? @maxandersen am I right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no plan to make this public. It's more likely that we'll move it to a separate repository.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whats the problem you for see @gsmet ? I feel like i'm missing some context ;)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest I am not sure why this line was removed. I am more than fine adding it back in if it fixes something :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooh - now i get it. yes you'll want to make sure you have a description either here or in quarkus-extension.yaml as otherwise it will show up blank on code.quarkus

@gsmet gsmet removed the backport? label Nov 14, 2019
@gsmet gsmet modified the milestones: 1.1.0, 1.0.0.Final Nov 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants