[
https://issues.apache.org/jira/browse/MWRAPPER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953387#comment-17953387
]
ASF GitHub Bot commented on MWRAPPER-158:
-----------------------------------------
lbruun commented on PR #166:
URL: https://github.com/apache/maven-wrapper/pull/166#issuecomment-2900598668
CI pipeline currently blocked by
[MWRAPPER-159](https://issues.apache.org/jira/browse/MWRAPPER-159)
> 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: Trivial
>
> 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)
