commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <>
Subject [jira] Commented: (COMMONSSITE-21) commons-parent-6 pom changes
Date Fri, 14 Dec 2007 12:57:43 GMT


Simon Kitching commented on COMMONSSITE-21:

I'm not sure this works right for NOTICE files. 

For example, commons-logging might include some code written by a third party but licensed
under an APL2.0-compatible license (including BSD, etc). In that  case AIUI we remove copyright
and license information from the files [1], and put it into NOTICE instead. This keeps the
code uncluttered, while putting the contributor info for the project ancestry into one easy-to-find
place (NOTICE.txt). 

So it is not just a matter of taking the organisation property from the pom; a single mvn
module can have multiple entries in its NOTICE file. 
To be doubly-clear: a single maven module (that is, a single pom.xml file) may correspond
to *many* lines of text in the NOTICE file, acknowledging every single copyright holder to
code contained in that single maven module. AFAIK, it is not possible or appropriate to put
one organization tag in a pom for every line we need in the NOTICE for that module.

For a notice inside a single JAR, I don't believe it is a legal requirement to acknowledge
the copyright holders of jars it depends on. In fact I would prefer to NOT do that. The dependency
information is explicitly present in the pom, and each of those dependent jars should contain
its own acknowledgements.

Whether an overall NOTICE is needed for a downloadable bundle that contains multiple jars
is debatable. I think not; there is a LICENSE file (APL2 of course) which is all that is relevant
for most people.

> commons-parent-6 pom changes
> ----------------------------
>                 Key: COMMONSSITE-21
>                 URL:
>             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,
> Opening this ticket to discuss changes for Version 6 of the commons-parent pom.
> See thread: 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.

View raw message