-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
support maven-wrapper like gradle-wrapper #3566
Comments
I think this is ready to be implemented but would need a community contribution 🙃 |
I think the |
First step is probably to add a |
Maven Wrapper has migrated from Takari to an official Maven project: https://maven.apache.org/wrapper/ |
As mentioned in this discussion @trystian1 and I are working on this feature. |
🎉 This issue has been resolved in version 34.111.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What would you like Renovate to be able to do?
A lot of new projects which are using maven relay on the maven-wrapper (https://github.com/takari/maven-wrapper) so maven behaves in the same way like gradle. you don't need to install a maven locally, it's just calling
./mvnw
and it will download the defined version inmaven-wrapper.properties
. So it would be really nice if there is also support for updating maven-wrapper. Maven wrapper consists of 4 files, 2 of them are stored in.mvn/wrapper/
directory the other two are the executables in the project root directoryDescribe the solution you'd like
solution should consist of two parts:
Describe alternatives you've considered
first thing can be achieved by manually changing the maven version number in maven-wrapper.properties
second thing can be also achieved by manually executing
mvn -N io.takari:maven:0.7.6:wrapper -Dmaven=3.3.3
where the version of maven is pinned to the currently used on and a new version of the wrapper is specifiedAdditional context
maybe the logic from the gradle-wrapper check can be reused and extended to cover both situations for maven (gradle uses only one version for the wrapper and the distribution)
The text was updated successfully, but these errors were encountered: