You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2021/12/05 14:03:00 UTC
[jira] [Updated] (MWRAPPER-16) update mvnw scripts to launch target Maven mvn scripts to enforce consistency
[ https://issues.apache.org/jira/browse/MWRAPPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MWRAPPER-16:
----------------------------------
Affects Version/s: 0.5.6
3.0.3
(was: 3.0.2)
> 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
> Affects Versions: 0.5.6, 3.0.3
> Reporter: Herve Boutemy
> Priority: Major
>
> 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)