[
https://issues.apache.org/jira/browse/COMMONSSITE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551809
]
Niall Pemberton commented on COMMONSSITE-21:
--------------------------------------------
The "ASF Source Header and Copyright Notice Policy" [1] deals with the contents
(example[2] from that doc) of the NOTICE file (is there any other relevant
policy docs?) - to be honest I find it a little vague since it uses words like
"may" rather than "must".
I agree though that for anything more complex than the AL2 its probably too
blunt an instrument - but do we have any components currently in commons that
have the scenarios you are bringing up? Because if we don't then isn't it
pointless raising theoretical objections. For me the remote resources plugin
isn't quite their yet - but down the road I could see it working well for most
components. The best solution IMO is what I suggested earlier - if the remote
resources plugin only generated a NOTICE file if there wasn''t already one
specified in the projects resources. That way components that needed all sorts
of 3rd party stuff could manually craft their NOTICE file - while the majority
just get it generated.
[1] http://www.apache.org/legal/src-headers.html
[2] http://www.apache.org/licenses/example-NOTICE.txt
> 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.
