You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lars Bruun-Hansen (Jira)" <ji...@apache.org> on 2025/05/22 09:52:00 UTC

[jira] [Updated] (MWRAPPER-158) Remove ASF header on generated maven-wrapper.properties

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

Lars Bruun-Hansen updated MWRAPPER-158:
---------------------------------------
    Priority: Major  (was: Trivial)

> Remove ASF header on generated maven-wrapper.properties
> -------------------------------------------------------
>
>                 Key: MWRAPPER-158
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-158
>             Project: Maven Wrapper
>          Issue Type: Bug
>          Components: Maven Wrapper Plugin
>            Reporter: Lars Bruun-Hansen
>            Priority: Major
>
> The Maven Wrapper Plugin will add an ASF license header on the generated {{maven-wrapper.properties}} file. I believe this is incorrect. It should have no license header.
> Reasoning: While the wrapper itself is licensed under ASF code, when used in a project (which may use any license!) the config for the wrapper's execution is surely not ASF (or even AL2). The file is generated by the plugin as a convenience. Similar to how some archetypes generate skeleton code. (comparison: Maven's own archetypes do _not_ add such a header)
> By contrast it makes sense to retain the license header on the script files. These for sure are ASF and the user is not meant to alter them.



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