cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-176) Add <libname>.LICENSE files
Date Sat, 18 Jul 2009 14:52:14 GMT

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


Mime
View raw message