-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.DR12, 7.1.0.DR13
-
None
-
Regression
-
-
-
-
-
-
mvnw stores maven to ~/.m2/wrapper directory. But customers could have denied access to .m2 folder. They could have allowed access only to .m2/repository, because they want to protect settings.xml file.
Our mvnw script should download maven to project directory.
Possible solution could be adding these two lines to .mvn/wrapper/maven-wrapper.properties:
distributionBase=PROJECT zipStoreBase=PROJECT
This issue is regression against EAP 7.0.0 and EAP 7.1.0.DR11.
FYI: unfortunately, distributionBase and zipStoreBase properties are not documented.
- is cloned by
-
WFLY-8175 mvnw wrapper shouldn't deppend on .m2/wrapper location
- Closed
- is related to
-
JBEAP-8839 Require Maven 3.3.1+ and introduce mvnw
- Closed
- relates to
-
JBEAP-8926 Make build scripts handle default settings.xml correctly
- Closed