-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Bring mvnw in line with the currently proposed Maven version 3.9.6 #37571
Conversation
What about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I don't want us to do that.
What are you doing exactly to get this warning?
Sorry the rationale is that |
Hm, so we are not eating our own dog food? Interesting. |
I'm just running |
I should have given more details, sorry, was working on something else. The new build cache we added is dependent on the version of Maven. If you want to use the build cache, you need to use the exact same version as the version used to produce the build cache. We want people using Maven and mvnd to be able to use the build cache, thus why we settled on 3.9.3. It's not ideal but it works. As for your suggestion of adding it to |
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
@gsmet Ok, thank for the details! What I still don't get is whether Maven 3.9.5 and mvnd 1.0-m8-m39 would work or not - or is it the caching setup itself that needs Maven 3.9.3? |
Looks like this was forgotten in the last few update PRs, so e.g. CI is still running with 3.9.3.
Noticed via the warning at the beginning of the build:
(I usually rely on sdkman)