Revert "Upgrade maven wrapper to maven 3.9.12" #1616
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 1ec7cbc.
Croway
approved these changes
Jan 8, 2026
Croway
reviewed
Jan 8, 2026
| @@ -1,4 +1,4 @@ | |||
| wrapperVersion=3.3.4 | |||
Contributor
There was a problem hiding this comment.
@gzurowski should this be updated like done in Camel repo? https://github.com/apache/camel/pull/20724/files#diff-1df564955cac198c2a317aceb01d86891160f1b185d9875b384b7d54819af358R17
Contributor
There was a problem hiding this comment.
I think you can have independent wrapper versions and maven versions. So we could keep 3.3.4 and then use maven 3.9.11 or go back to 3.3.2 also
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This reverts commit 1ec7cbc.
Multiple staging repositories were created in Nexus during the release process. Downgrading to Maven 3.9.11 resolves the issue.
See: https://issues.apache.org/jira/browse/CAMEL-22826