[
https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050696#comment-13050696
]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I'm going away 17->27 June unable to develop. Sadly, I'm not going to be able
to finish in time. I'll give some instructions so that people can step in and
hopefully roll a beta which I'm away.
Build container-spring and review the DEPENDENCIES generated.
Within the "From: 'an unknown organization'" section, I read only a handful of
jars without organisational and licensing meta-data. I suspect these are all
Oracle jars released under CDDL+GPL from Project Glassfish but this needs to be
checked.
Add organisational and licensing meta-data for these jars to
src/main/appended-resources/supplemental-models.xml
and then create a new section (CDDL) in LICENSE for them (take a look at how
the others are done) by editing
container-spring/src/main/licensing/license-for-binary.txt
Then go through the DEPENDENCIES and add the information in a similar fashion
to the start I made. (The Apache jars are not third party resources and don't
need to be listed)
Once this is done, then everything else in the distribution which isn't
described in the LICENSE needs to be reviewed, audited and appropriate stuff
added to LICENSE and NOTICE.
> Create a correct NOTICE/LICENSE files for the spring binary artifact
> (currently having bad contents)
> ----------------------------------------------------------------------------------------------------
>
> Key: JAMES-1269
> URL: https://issues.apache.org/jira/browse/JAMES-1269
> Project: JAMES Server
> Issue Type: Bug
> Affects Versions: 3.0-M2
> Reporter: Stefano Bagnara
> Priority: Blocker
> Fix For: 3.0-beta1
>
> Attachments: DEPENDENCIES
>
>
> Our first attempt to release beta1 didn't include a LICENSE/NOTICE at all.
> Current trunk includes a plain LICENSE/NOTICE tuple with just ASF
> "references".
> We have to reintroduce complete LICENSE/NOTICE files in the binary
> distribution as we include third party dependencies in that package.
> Subtask: we have to make sure we correctly document the way JSW artifacts are
> included and what their license is (and the fact that appassembler doesn't
> include licensing informations about itself and the JSW content they took
> from the tanuki wrapper).
> I uploaded the tanuki wrapper version 3.2.3 I obtained under the MIT license
> here:
> http://people.apache.org/~bago/third-party/
> I compared the content of "my" wrapper with the content in the
> "org\codehaus\mojo\appassembler\daemon\jsw" folder inside the
> org.codehaus.mojo/appassembler-maven-plugin-1.0.jar maven plugin (the files
> our build process includes in the binary) and they are bitwise identical.
> So we have to review the lib folder from the current trunk and make sure we
> correclty identify LICENSE/NOTICE requirement for them (for sure we have to
> add the MIT licensing for the tanuki wrapper code we include, but probably we
> have other artifacts to be attributed to the copyright holders and the
> respective licenses under we redistribute them).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
