cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <>
Subject [jira] [Commented] (COCOON-2330) Release separate source and dependencies packages
Date Thu, 07 Feb 2013 15:07:13 GMT


Francesco Chicchiriccò commented on COCOON-2330:

Not completely: I still believe we need to separate LICENSEs and NOTICEs.

I'd change your latest proposal as:

 * use current LICENSE.txt and NOTICE.txt for src package

 * create legal-deps/LICENSE.txt and legal-deps/NOTICE.txt being the merge of all legal/*.license.txt
under the following conditions:

  1. do not repeat the same license more than once: if the EPL license is already there for
dependency X, just say "dependency Y released under EPL, see above"

  2. split the content of current legal/$1.txt between LICENSE and NOTICE; for example the
content of 'jfor-0.7.1.jar.license.txt' will become

  This product includes software developed by the jfor project.
 Copyright (c) 2002 by the jfor project. All rights reserved.

(the rest of jfor-0.7.1.jar.license.txt's content)

...and finally remove the whole legal subdir.

> 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