maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Cole (JIRA)" <>
Subject [jira] [Commented] (MNG-5937) Maven-Wrapper for unified project environments (analog the Gradle wrapper)
Date Tue, 19 Feb 2019 00:50:00 GMT


Adrian Cole commented on MNG-5937:

I would consider the maven wrapper a backdoor required feature. I like it, but it is troubling
that the team is not able to donate this to the ASF, and even are going so far as to suggest
every ASF project needs to advertise it in their NOTICE file. We don't have this behavior
even from gradle.. maybe they would like to have projects add GradleWare to the NOTICE file,
too? Maybe they will one day!

Anyway, maven should be fully functional, and I'd argue that at this point wrapper is a part
of it being functional. I think the community should be at least permitted to write their
own version of the wrapper if the takari folks are unwilling.

> Maven-Wrapper for unified project environments (analog the Gradle wrapper)
> --------------------------------------------------------------------------
>                 Key: MNG-5937
>                 URL:
>             Project: Maven
>          Issue Type: Improvement
>          Components: Command Line
>            Reporter: Robert Weiser
>            Priority: Major
>             Fix For: 3.7.0-candidate
> It would be nice to provide a wrapper for maven which behaves similarily to the wrapper
Gradle has. This would allow projects to share Maven in a certain version along with some
project-specific Maven options like for example the location of the user or the global settings
files or the maximum java heap size to use.
> There already are projects on github (e.g.:
providing said feature, however it would be nice to have it developed and maintained by the
very people providing us with the offical Maven release.
> Cheers, Robert

This message was sent by Atlassian JIRA

View raw message