[
https://issues.apache.org/jira/browse/COCOON-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569598#comment-13569598
]
Francesco Chicchiriccò commented on COCOON-2330:
------------------------------------------------
Cédric, I've been watching several question like yours while Syncope was still
in the incubator.
In our case, LICENSE & NOTICE for the source package are already fine (just the
ones currently on the root of source tree).
For the -deps package, however, we need to provide different LICENSE & NOTICE
that will report license and copyright information for each of the JAR files
contained.
FYI, take a look at the discussion [1] about Apache ManifoldCF [2] which
releases for download a source package, a binary package (not our case) and a
"lib" package whose purpose is the same of the -deps package we are discussing
here.
As an example of the content of our -deps LICENSE and NOTICE files, you can
take a look at LICENSE and NOTICE files contained in [3].
[1]
http://old.nabble.com/Binary-dependencies-in-source-releases-(Was%3A--VOTE--Release-ManifoldCF-0.5-incubating,-RC0)-td33579703.html
[2] http://manifoldcf.apache.org/en_US/download.html
[3]
http://www.apache.org/dyn/closer.cgi/manifoldcf/apache-manifoldcf-1.0.1-lib.tar.gz
> Release separate source and dependencies packages
> -------------------------------------------------
>
> Key: COCOON-2330
> URL: https://issues.apache.org/jira/browse/COCOON-2330
> 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] http://markmail.org/message/f6rm2ca35eiraf7i
--
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: http://www.atlassian.com/software/jira
