[
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.
