[
https://issues.apache.org/jira/browse/MWRAPPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512979#comment-17512979
]
Herve Boutemy commented on MWRAPPER-16:
---------------------------------------
MWRAPPER-61 goes one step beyond: it even removes the need for maven-wrapper.jar
> update mvnw scripts to launch target Maven mvn scripts, to enforce consistency
> ------------------------------------------------------------------------------
>
> Key: MWRAPPER-16
> URL: https://issues.apache.org/jira/browse/MWRAPPER-16
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Scripts
> Affects Versions: 0.5.6, 3.1.0
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: 3.2.0
>
>
> currently, wrapper scripts copied to user project mimic Maven scripts (search
> .mvn, and so on), then launch wrapper.jar: at the end, wrapper.jar calls
> installed Maven distribution Classworlds bootstrap to run Maven Java code
> this may cause a discrepency between features supported by mvnw script vs
> what would have been done by installed Maven mvn scripts
> for example, when/if [https://github.com/apache/maven/pull/602] is done
> To enforce consistency, mvnw should launch installed Maven mvn script at the
> end, and let it do its full work as if it had been launched
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
