apache-jar-resource-bundle NOTICE file is not consistent with apache policy
---------------------------------------------------------------------------
Key: MRRESOURCES-32
URL: http://jira.codehaus.org/browse/MRRESOURCES-32
Project: Maven 2.x Remote Resources Plugin
Issue Type: Bug
Affects Versions: 1.0-beta-2
Reporter: David Jencks
Attachments: apache-jar-resource-bundle.diff
Recent discussions on the apache legal-discuss list have made it extremely
clear that the generated NOTICE file from the current (1.3)
apache-jar-resource-bundle is not consistent with apache policy on contents of
NOTICE files.
After working hard to clarify what the policy might be I've come up with a
bundle whose output has not produced any objections. We're using this
currently in geronimo but would like to get this into a more global location
for an imminent apacheds release.
The main change is that the NOTICE file contains only the apache notice. You
can append other notices using the appended-resources directory. This
corresponds to the policy that the NOTICE file apply to exactly what is
actually in the jar, not at all to any dependencies it may need to actually be
used, and that the NOTICE file not have any excess verbiage such as horizontal
rules or explanatory text.
The dependencies are listed by license in an additional informative
DEPENDENCIES file.
There are a couple weird things that it would be great if someone could figure
out:
- I can't get a blank line between the project name and the notice in the
NOTICE file
- I can't figure out how to configure a projectName so it is used in the NOTICE
file project name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
