[
https://issues.apache.org/jira/browse/COMMONSSITE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552044
]
Dennis Lundberg commented on COMMONSSITE-21:
--------------------------------------------
I've been reading through the links that have been provided regarding license
and notice files. Great pointers by the way. I was hoping to find some guidance
regarding the naming of these files.
http://apache.org/dev/apply-license.html#license-file-name
"Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt?
This is permitted. However the preference is that the files be called
LICENSE and NOTICE."
I doubt that the apache-jar-resource-bundle will be altered to go against the
recommendation, so will probably not happen. In light of that I'd say that
option 3 is the way to go. It is a one-time-change for each component.
It is nice to not have to configure too much. Just drop in a replacement NOTICE
file (or LICENSE file) and it will be used. We must make sure to document it in
our build/release docs.
> commons-parent-6 pom changes
> ----------------------------
>
> Key: COMMONSSITE-21
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-21
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Niall Pemberton
> Attachments: commons-valdiator-generated-NOTICE.txt,
> COMMONSSITE-21-commons-parent-pom-v1.patch,
> COMMONSSITE-21-commons-parent-pom-v2.patch
>
>
> Opening this ticket to discuss changes for Version 6 of the commons-parent
> pom.
> See thread: http://tinyurl.com/39eo9z for related discussion/issues
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
