[ 
https://issues.apache.org/jira/browse/BROOKLYN-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137015#comment-14137015
 ] 

Alex Heneveld commented on BROOKLYN-21:
---------------------------------------

Detailed analysis by @frontiertown at 
http://mail-archives.apache.org/mod_mbox/brooklyn-dev/201409.mbox/%3ccabqfki3gazu9jjimz7x5yvk2npfwvubxoumav97d5rk5+x9...@mail.gmail.com%3E
 .

My understanding is that the only action required for the maven dependencies is 
to (1) exclude JNA from jclouds.  (I am curious how Apache jclouds deal with 
this!)  The test dependencies are clear as they are optional at compile time 
and not included in the binary artifacts (thus not redistributed).  The 
BeanShell dependency is fine because it is dual-licensed (I think it is also 
test-only).

Also (2) note BROOKLYN-61 regarding JS licenses.

Finally (3) do any of these require additional text to be included in the 
NOTICE (BROOKLYN-17) ?

> Verify licenses of dependencies
> -------------------------------
>
>                 Key: BROOKLYN-21
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-21
>             Project: Brooklyn
>          Issue Type: Sub-task
>            Reporter: Richard Downer
>            Assignee: Richard Downer
>             Fix For: 0.7.0-M2
>
>
> Our dependencies must be compatible with ASF licensing policy; see: 
> https://www.apache.org/legal/resolved.html
> A slightly looser standard may apply in some cases, see:
>   * 
> https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201406.mbox/%3CCAOGo0VbmxVZgDnJAoUhUYuXMUobHN_sQgAaTX4ThhRbzgA2aEw%40mail.gmail.com%3E
>   * 
> https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201406.mbox/%3CCAM1oqKqZqxmAM8yt%2BD0d0UJ_AfibxiCAbcRPsU0FL8xSpLHQFA%40mail.gmail.com%3E
>   * 
> https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201406.mbox/%3CCAM1oqKqDDj_tHmu5UuPQumbc%2Bj4Bb0aGPpwmeJu47k6WguoWcA%40mail.gmail.com%3E
> This may be useful for test-scoped dependencies (e.g. the LGPL MySQL JDBC 
> driver), as long as we ensure that the user has to undertake an "informed 
> action" to start using the non-policy-compliant dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to