You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2011/06/13 19:32:51 UTC
[jira] [Created] (JAMES-1269) Create a correct NOTICE/LICENSE files
for the spring binary artifact (currently having bad contents)
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
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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Eric Charles (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049780#comment-13049780 ]
Eric Charles commented on JAMES-1269:
-------------------------------------
https://twitter.com/#!/ApacheJames/status/80998806761639938
Some encouragements for the last mile :)
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050400#comment-13050400 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
Perhaps replace with standard @SuppressWarnings
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050335#comment-13050335 ]
Norman Maurer commented on JAMES-1269:
--------------------------------------
After looking in the DEPENDENCIES file I think we must remove this:
com.google.code.findbugs:annotations:jar:1.3.9
License: GNU Lesser Public License (http://www.gnu.org/licenses/lgpl.html)
its LGPL which is not allowed
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048745#comment-13048745 ]
Stefano Bagnara commented on JAMES-1269:
----------------------------------------
Not sure when I will have enough time for the whole task. So if you have time go ahead. If I don't see this task assigned I will assign to me as soon as I find some time to do some 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049119#comment-13049119 ]
Stefano Bagnara commented on JAMES-1269:
----------------------------------------
The assembly creates a "DEPENDENCIES" file using data from dependencies poms and data specified in the supplemental-models.xml file. Probably that file can be used as a reference to copy text for the LICENSE and NOTICE files.
It would be good to have a quick reference to know what licenses requires attribution text in NOTICE and what instead simply requires a reference to the license in the LICENSE file.
It's weird no one attempted to write a maven plugin to take care of this: for a skilled maven plugin developer it should be really easy to do. Maybe such a tool would give a false sense of "compliance", don't know.
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049187#comment-13049187 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I'm almost out of time today. Unless someone else beats me to it or comes up with a better plan, I'll start working on these issues by creating a tool.
But opinions, ideas and objections welcomed :-)
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050365#comment-13050365 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
eric: The format required to add the missing information to DEPENDENCIES has a very high level of replication and is hard to maintain. Ideally, the information would be maintained concisely and then used to fix DEPENDENCIES and generate appropriate NOTICE and LICENSE documents.
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Closed] (JAMES-1269) Create a correct NOTICE/LICENSE files
for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin closed JAMES-1269.
----------------------------------------
> 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
> Assignee: Robert Burrell Donkin
> Priority: Blocker
> Fix For: 3.0-beta3
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Eric Charles (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050376#comment-13050376 ]
Eric Charles commented on JAMES-1269:
-------------------------------------
The findbug dependency comes from AbstractStateMailetProcessor in mailet-container-library
There is an annotation @edu.umd.cs.findbugs.annotations.SuppressWarnings(value = "NP_LOAD_OF_KNOWN_NULL_VALUE", justification = "HashMap allows the null key")
Option 1: exclude findbug from container-spring
Option 2: completely remove it from mailet-container-library, and also remove the annotation.
If findbug is LGPL, I guess we must go for option 2.
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050397#comment-13050397 ]
Norman Maurer commented on JAMES-1269:
--------------------------------------
Yeah we should just remove it..
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049105#comment-13049105 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I'm thinking of throwing together a tool to help.
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051023#comment-13051023 ]
Norman Maurer commented on JAMES-1269:
--------------------------------------
I just checked we don't need the jaxb-* jars anymore. The same is true for the servlet-api jar. So we should just remvoe them
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Eric Charles (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050428#comment-13050428 ]
Eric Charles commented on JAMES-1269:
-------------------------------------
LGPL findbug dependency removed.
http://svn.apache.org/viewvc?rev=1136439&view=rev
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050363#comment-13050363 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
eric: Too much of the required meta-data is missing
I'm currently auditing the dependencies and adding in what's missing.
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048714#comment-13048714 ]
Norman Maurer commented on JAMES-1269:
--------------------------------------
you are right... Will you work on this, or should I tackle it ?
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050362#comment-13050362 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
norman: yep
(I'm going through the contents of the binary ATM, and plan to add excludes)
Anyone know what it's used for?
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049668#comment-13049668 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I'm sure there is but I don't know of any which is released. I've started talking but realistically a donation to Rat and then a release will take weeks.
I've written quite a few tools like this before and I hope to be able to hack an independent tool today that is tuned to James. This should allow us to release the beta sooner than that time frame.
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049046#comment-13049046 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I cleaned the top level LICENSE and NOTICE files, removing anything that didn't match the contents of trunk at this time. I think we're going to need to craft LICENSE and NOTICE files for the binary release.
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049125#comment-13049125 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I would prefer a separate tool to check compliance but IMHO a tool that just assembled LICENSE and NOTICE documents correctly based on the actual contents would be very useful and not difficult to write. Anyone want to help me?
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Updated] (JAMES-1269) Create a correct NOTICE/LICENSE files
for the spring binary artifact (currently having bad contents)
Posted by "Eric Charles (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Charles updated JAMES-1269:
--------------------------------
Attachment: DEPENDENCIES
Can the attached file be used to generate our NOTICE and LICENSE file.
Can someone explain on to do it. What must go to NOTICE, what must go to LICENSE ?
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051015#comment-13051015 ]
Stefano Bagnara commented on JAMES-1269:
----------------------------------------
I'm stuck at the jaxb-impl jar. Downloading the jar from jaxb.java.net gives me a big jar, once "installed" I find a big folder including the jar we bundle and much more. This big folder has a License.txt including the CDDL+GPL+ClassException license and then has ThirdPartyLicenseReadme.txt including a lot of licenses for stuff in the folder. My main concern is about "XML-NamespaceSupport" under the "Artistic License" but I can't understand if this is a licensing for something else in that folder or if it is the licesing for some code used for the jar we really use.
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050436#comment-13050436 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I have a appointment with the physio and don't expect to be back until later this evening, so I'll outline what I'm doing. Take a look at the commit record for more details.
The LICENSE and NOTICE distributed with the binary need to be quite different. So, I've add version to the source:
container-spring/src/main/licensing/license-for-binary.txt
container-spring/src/main/licensing/notice-for-binary.txt
Maven is missing a lot of the provenance meta-data required. I'm reviewing and auditing a group of dependent jars from an upstream vendor. (In some cases, this means finding and download the original release then verifying checksums see spring sections for details.) Next check that the license is okay. Then updating
src/main/appended-resources/supplemental-models.xml
with just the missing information. Then adding licensing details to LICENSE. If the LICENSE requires additions to NOTICE, I add them but try to keep the NOTICE clean.
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051085#comment-13051085 ]
Stefano Bagnara commented on JAMES-1269:
----------------------------------------
I worked around the issue: instead of documenting the licensing I've been able to remove all of the artifact listed under the "an unknown organization" section ;-)
Robert, you say "everything else in the distribution which isn't described in the LICENSE needs to be reviewed". Can you tell what artifacts did you already checked and what is missing?
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049664#comment-13049664 ]
Norman Maurer commented on JAMES-1269:
--------------------------------------
@Robert:
Why do we need to write a special tool for it and not just use the maven assembly/remote-resources plugin to generate this kind of stuff.
I can't believe we are the only project which needs this and so there "must" be some tool already ;)
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049044#comment-13049044 ]
Robert Burrell Donkin commented on JAMES-1269:
----------------------------------------------
I'll switch the licensing review work I've been doing on the container to this JIRA.
> 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
>
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Resolved] (JAMES-1269) Create a correct NOTICE/LICENSE
files for the spring binary artifact (currently having bad contents)
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin resolved JAMES-1269.
------------------------------------------
Resolution: Fixed
Assignee: Robert Burrell Donkin
The application is now released from a separate project.
> 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
> Assignee: Robert Burrell Donkin
> Priority: Blocker
> Fix For: 3.0-beta3
>
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org