[jboss-jira] [JBoss JIRA] (WFLY-8175) mvnw wrapper shouldn't deppend on .m2/wrapper location

[Peter Palaga (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga moved JBEAP-8985 to WFLY-8175:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8175  (was: JBEAP-8985)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Build System
                       Test Suite
                           (was: Build System)
                           (was: Test Suite)
    Affects Version/s:     (was: 7.1.0.DR12)
      Affects Testing:   (was: Regression)


> mvnw wrapper shouldn't deppend on .m2/wrapper location
> ------------------------------------------------------
>
>                 Key: WFLY-8175
>                 URL: https://issues.jboss.org/browse/WFLY-8175
>             Project: WildFly
>          Issue Type: Bug
>          Components: Build System, Test Suite
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>            Priority: Critical
>
> 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:
> {noformat}
> distributionBase=PROJECT
> zipStoreBase=PROJECT
> {noformat}
> This issue is regression against EAP 7.0.0 and EAP 7.1.0.DR11.
> FYI: unfortunately, [distributionBase|https://github.com/takari/maven-wrapper/blob/master/src/main/java/org/apache/maven/wrapper/WrapperExecutor.java#L32] and [zipStoreBase|https://github.com/takari/maven-wrapper/blob/master/src/main/java/org/apache/maven/wrapper/WrapperExecutor.java#L34] properties are not documented.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)