You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/04/21 10:44:00 UTC

[jira] [Updated] (MWRAPPER-109) mvnw needs some feature to support different URLs to download mvn from

     [ https://issues.apache.org/jira/browse/MWRAPPER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak updated MWRAPPER-109:
-------------------------------------
    Description: 
Just like a Maven project, that may be built "standalone", but also may be redirected to some MRM (in some sealed environment, no internet just MRM accessible, using settings.xml), so basically a project can be made build-able in both but when mvnw used, this is not possible as it sticks to only one distributionUrl.

As wrapper.properties either point to this or that. And in example above, it is either central accessible but not the MRM, or central is not accessibly only the MRM.

  was:
Just like a Maven project, that may be built "standalone", but also may be reidrected to some MRM (in some sealed environment, no internet just MRM accessible, using settings.xml), so basically a project can be made buildable in both but when mvnw used,. this is not possible.

As wrapper.properties either point to this or that. And in example above, it is either central accessible but not the MRM, or cenrtal is not accessiblt only the MRM.


> mvnw needs some feature to support different URLs to download mvn from
> ----------------------------------------------------------------------
>
>                 Key: MWRAPPER-109
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-109
>             Project: Maven Wrapper
>          Issue Type: Improvement
>          Components: Maven Wrapper Plugin
>            Reporter: Tamas Cservenak
>            Priority: Major
>
> Just like a Maven project, that may be built "standalone", but also may be redirected to some MRM (in some sealed environment, no internet just MRM accessible, using settings.xml), so basically a project can be made build-able in both but when mvnw used, this is not possible as it sticks to only one distributionUrl.
> As wrapper.properties either point to this or that. And in example above, it is either central accessible but not the MRM, or central is not accessibly only the MRM.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)