[
https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051500#comment-13051500
]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
The LICENSE (in the binary) contains information for all third party resources
included in the binary that I've audited.
Once the DEPENDENCIES have all the information required, it should be quick and
easy to add information for the dependencies copied into lib and every ASF jar.
Where everything else in the binary comes from needs to be audited. It's
probably a good idea to create some sub-tasks for these resources so that we
can track progress.
> 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: [email protected]
For additional commands, e-mail: [email protected]
