ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (JIRA)" <>
Subject [jira] [Commented] (ACE-211) Review and improve NOTICE and LICENSE files
Date Wed, 24 Apr 2013 12:19:15 GMT


Bram de Kruijff commented on ACE-211:

Alright again :) Based on feedback and another detailed review through the packages, I have
updated all LICENSE and NOTICE files founds in build/resources/<src/bin/deps>. These
are the highlights, more details in the commits and files themselves;

1) Added an extra copyright statement on the OSGi software notice
2) Added CDDL & JCraft license to the bn/deps LICENSE
3) Added additional usage/copyright notices for all included artifacts (such as testng / jclouds
/ bouncy castle)
4) Bubbled some additional NOTICE statement from ALS2 licensed resources.

On the Bouncy Castle matter Jan Willem said;

There has been some discussion on the legal-discuss ML about how to
proceed, see
<> and
<> for
an overview. There is also a JIRA issue about this as well:

IIRC, the situation is that adding a clause for Apache ACE on the
legal exports-page *should* be sufficient. However, I still haven't
had confirmation about this, perhaps any of the PMCs can ping legal again?

After browsing those threads and issue there does not seem to be any activity on that. At
this point I have settled for the appropriate notices, which is basically the same as what
for exmaple SOLr does.
> Review and improve NOTICE and LICENSE files
> -------------------------------------------
>                 Key: ACE-211
>                 URL:
>             Project: ACE
>          Issue Type: Task
>          Components: Build
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
> During the vote for 0.8.1-incubator on the mailing list, in the discussion thread, there
were some improvements suggested to a few of the NOTICE and LICENSE files. For reference,
see . This task is there so we don't forget to
make those improvements before our next release.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message