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 Tue, 05 Feb 2013 18:02:11 GMT


Francesco Chicchiriccò commented on COCOON-2330:

As stated in [1], "LICENSE and NOTICE belong at the top level of the source tree. They may
be named LICENSE.txt and NOTICE.txt, but the bare names are preferred."

Moreover, in [2] "The NOTICE file is described in section 4.4 of the Apache License version
2.0. It presence is not mandated by the license itself, but by ASF policy."

Basically, this means that LICENSE and NOTICE *must* be delivered at top level of every package
release. So, both -src and -deps in our case.

The legal/* stuff is something that I guess was established before this ruling was stated
clearly in its definitive form.

If you take a look at ManifoldCF release files [3] and [4] you can see how they solved the
same issue: the -src package comes with "simple" LICENSE and NOTICE at root level + lib-license/
subdir containing "rich" LICENSE and NOTICE while the -lib (i.e. the -deps) packages comes
with "rich" LICENSE and NOTICE at root level.

This means of course that
 1. when extracting the -src package, LICENSE and NOTICE are "simple"
 2. when extracting the -deps package alone, LICENSE and NOTICE are "rich"
 3. when extracting the -deps package over the -src package, LICENSE and NOTICE are "rich",
as it should be since the "rich" version fully includes the "simple" version

> 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