cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Damioli (JIRA) <>
Subject [jira] [Commented] (COCOON-2330) Release separate source and dependencies packages
Date Thu, 07 Feb 2013 14:11:15 GMT


Cédric Damioli commented on COCOON-2330:

I'm fully ok with what you said, but even after reading,
I still don't understand what I'm supposed to put in the "rich" NOTICE file. It seems that
my understanding of legal english is inadequate ! :)
I don't know how to understand "Aside from Apache-licensed dependencies which supply NOTICE
files of their own, it is uncommon for a dependency to require additions to NOTICE.". Does
it mean that for Apache-licensed dependencies, NOTICE files has to be merged ?
In your ManifoldCF example, the "rich" NOTICE file is the same that the "light" one, and Apache-licensed
dependencies are not listed in that particular file, but in the LICENSE file.

What I propose concretely to do:
 - leave NOTICE.txt as is and include in both "src" and "deps" packages : it will be at the
root of both packages
 - leave LICENSE.txt as is in the "src" package
 - create a legal/LICENSE.txt being the merge of all legal/*.license.txt based on the model
of ManifoldCF. At build time, this file will be put at the root of the the "deps" package.
 - remove all legal/*.license.txt

do you agree ?

> Release separate source and dependencies packages
> -------------------------------------------------
>                 Key: COCOON-2330
>                 URL:
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: - Build System: Ant
>    Affects Versions: 2.1.11
>            Reporter: Francesco Chicchiriccò
>             Fix For: 2.1.12
> As recently reported by David Corssley [1] the 2.1.X release must comply with ASF policies
about releases, in particular providing a separate source code package (without any external
JAR file inside) and dependencies package (with all external JAR files) for distribution.
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message