You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Johan Oskarsson (JIRA)" <ji...@apache.org> on 2009/05/14 17:16:45 UTC
[jira] Created: (CASSANDRA-176) Add .LICENSE files
Add <libname>.LICENSE files
---------------------------
Key: CASSANDRA-176
URL: https://issues.apache.org/jira/browse/CASSANDRA-176
Project: Cassandra
Issue Type: Task
Affects Versions: 0.3
Reporter: Johan Oskarsson
Fix For: 0.3
To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732908#action_12732908 ]
Henri Yandell commented on CASSANDRA-176:
-----------------------------------------
I'm interested in why lib/ is bad. My personal view is:
lib/<project>-<version>/LICENSE
lib/<project>-<version>/foo.jar
lib/<project>-<version>/other files related to <project>
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711160#action_12711160 ]
Jonathan Ellis commented on CASSANDRA-176:
------------------------------------------
in the future, let's patch things that need to go against both 0.3 and trunk against 0.3, to keep things sane.
one source of licensing is sufficient. two is asking for inconsistencies. do you want a license file per jar, or notice file?
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-176) Add .LICENSE files
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Oskarsson updated CASSANDRA-176:
--------------------------------------
Attachment: CASSANDRA-176.patch
This patch adds one license file per jar in trunk, except for activation.jar that should have been removed as per CASSANDRA-186.
Looking at this document: http://www.apache.org/legal/resolved.html it seems that public domain (high-scale-lib.jar) is ok to include.
We should probably also add licensing information to the notice file as per CASSANDRA-122
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710940#action_12710940 ]
Johan Oskarsson commented on CASSANDRA-176:
-------------------------------------------
With all the related tickets closed, my only question mark now is the high-scale-lib.jar under this license: http://creativecommons.org/licenses/publicdomain/ - is it allowed to be included?
It is not listed here http://www.apache.org/legal/3party.html, if nobody knows I suggest we create a ticket in LEGAL
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Fix For: 0.3
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711175#action_12711175 ]
Johan Oskarsson commented on CASSANDRA-176:
-------------------------------------------
Personally I would prefer one licensing per file in that case, gives easy access and a quick overview by looking at the directory, easy to spot missing licensing files if there is a jar without one.
That said, I don't know if we are required to put something in notices for the non BSD/Apache2 licensed jars. I'll leave that up to someone more experienced
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709428#action_12709428 ]
Jonathan Ellis commented on CASSANDRA-176:
------------------------------------------
let's put them in lib/licenses then, imo it's too cluttered all in lib/
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Fix For: 0.3
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709454#action_12709454 ]
Eric Evans commented on CASSANDRA-176:
--------------------------------------
See also https://issues.apache.org/jira/browse/CASSANDRA-122 (which is duplicate of this issue).
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Fix For: 0.3
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-176) Add .LICENSE files
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-176:
-------------------------------------
Component/s: Core
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.4
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709439#action_12709439 ]
Johan Oskarsson commented on CASSANDRA-176:
-------------------------------------------
This is what I found out through some quick googling and from memory, please review to make sure I haven't missed anything.
Apache:
commons-cli-1.1.jar
commons-collections-3.2.1.jar
commons-javaflow-1.0-SNAPSHOT.jar
commons-lang-2.4.jar
commons-logging-1.0.4.jar
commons-math-1.1.jar
lucene-core-2.2.0.jar
libthrift.jar
zookeeper-3.0.0.jar
log4j-1.2.15.jar
groovy-1.5.6.jar
BSD
antlr-3.1.3.jar
stringtemplate-3.0.jar
jline-0.9.94.jar
Common Public License - v 1.0
junit-4.6.jar
LGPL:
http://martiansoftware.com/jsap/license.html
JSAP-2.1.jar
http://sourceforge.net/project/shownotes.php?release_id=180015
pcj.jar
Public domain:
high-scale-lib.jar
Google suggest it is the sleepycat license, never heard of it:
http://asm.ow2.org/license.html
http://www.opensource.org/licenses/sleepycat.php
asm-all-2.2.1.jar
Unknown:
activation.jar
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Fix For: 0.3
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711179#action_12711179 ]
Jonathan Ellis commented on CASSANDRA-176:
------------------------------------------
i am ok with
- notice.txt approach
- lib/licenses/ approach
not ok w/ putting licenses directly in lib/.
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711181#action_12711181 ]
Jonathan Ellis commented on CASSANDRA-176:
------------------------------------------
(but i can mv the licenses to the subdir myself if that is the approach we decide on, i'm not asking for a resubmitted patch :)
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709443#action_12709443 ]
Johan Oskarsson commented on CASSANDRA-176:
-------------------------------------------
* If my findings are correct we have two LGPL jar files, those are not allowed and will have to be removed iirc
* Apparently the sleepycat license is not allowed either.
* activation.jar is under Sun Microsystems, Inc. Binary Code License Agreement according to some random site, is that allowed?
See: http://www.apache.org/legal/3party.html
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Fix For: 0.3
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-176) Add .LICENSE files
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714063#action_12714063 ]
Johan Oskarsson commented on CASSANDRA-176:
-------------------------------------------
I'm fine with them in lib/licenses even though it makes it tricky to spot missing licenses.
> Add <libname>.LICENSE files
> ---------------------------
>
> Key: CASSANDRA-176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-176
> Project: Cassandra
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.3
>
> Attachments: CASSANDRA-176.patch
>
>
> To make sure we are clear on the license of each of the jar files in the project we could add a license file for each of the jarfiles. For example, the jar commons-collections-3.2.1.jar would have a file next to it called commons-collections-3.2.1.LICENSE
> Example: http://svn.apache.org/repos/asf/hadoop/hive/trunk/lib/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.