Lars Bruun-Hansen opened MWRAPPER-158 and commented
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.
Remote Links:
Lars Bruun-Hansen opened MWRAPPER-158 and commented
The Maven Wrapper Plugin will add an ASF license header on the generated
maven-wrapper.propertiesfile. 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.
Remote Links: