Set maven version like maven-wrapper
See original GitHub issueTo ensure repeatable builds in a CI environment it would be great to be able specify desired maven version, like the Maven Wrapper plugin.
Or possibly detect if mvnw
is present in the project directory and use that?
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
A Quick Guide to Maven Wrapper - Baeldung
The Maven Wrapper is an excellent choice for projects that need a specific version of Maven (or for users that don't want to...
Read more >Getting Started with Maven Wrapper - {Java} Streets
To upgrade the maven version in the existing wrapper, you can use -Dmaven=<version> argument and re-run the wrapper:warpper goal. Assuming that ...
Read more >Run Your Maven Build Anywhere with the Maven Wrapper
The .mvn/wrapper directory has a jar file maven-wrapper.jar that downloads the required version of Maven if it's not already present. It ...
Read more >Set maven version like maven-wrapper · Issue #143 - GitHub
A tool similar to Maven's wrapper plugin ( mvn -N io.takari:maven:0.7.7:wrapper ) would generate mvndw and mvndw.cmd scripts; Those scripts ...
Read more >Maven | IntelliJ IDEA Documentation - JetBrains
Use the Maven wrapper or a custom version of Maven ... On the Maven settings page, in the Maven home directory field, specify...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It is true that we embed Maven, but we modify it slightly. Pulling a random Maven version during the build and running with it would be rather risky because we test only against a single particular Maven version.
Providing our own
mvndw
script that would pull a specific version ofmvnd
would perhaps solve your problem too? I think that kind of solution would be more robust and I’d be open to accept such a contribution.Thinking about it this would maybe be better placed in the Maven-wrapper project? Since it downloads maven versions anyway, it might be easier to modify that script to either download the regular maven binary or a
mvnd
?