Upgrade jclouds from 2.5.0 to 2.6.0 #567
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverting #447, since 2.6.0 contains the fix for JCLOUDS-1620.
jclouds 2.6.0 requires Guice 7.0.0, which is above the version delivered by core (6.0.0), but so far I have found no issue ignoring the upper bounds error and continuing to deliver Guice 6.0.0. Guice 6.0.0 supports both
javax
andjakarta
imports, while 7.0.0 drops support forjavax
, so 6.0.0 makes more sense for Jenkins. Unfortunately this required adding a few temporary workarounds to the POM file.Testing done
mvn clean verify
, includingMinioIntegrationTest
I would appreciate if someone could do a manual test run with an AWS account, since I believe CI unfortunately is not enough.