You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2006/03/27 09:48:22 UTC

[jira] Closed: (TUSCANY-44) Resolve licensing issue with Rhino for JavaScript container

     [ http://issues.apache.org/jira/browse/TUSCANY-44?page=all ]
     
ant elder closed TUSCANY-44:
----------------------------

    Resolution: Fixed

Had this reply over on legal-discuss:

http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200603.mbox/%3cPine.LNX.4.61.0603241707280.19669@kongo%3e

and also a much longer mail from Cliff that doesn't seem to have made it to the archive yet:

"my approach was to start with it excluded (requiring it to be removed from future releases within one year) and see if there's anyway to get Rhino replaced or relicensed in the next six months.  If this isn't possible, then we have six more months before the current policy would require releases to exclude Rhino, but we may also decide that it just isn't practical or worth the benefit, and should therefore create some sort of exception, like one of the ones above."

So I'd say right now we do nothing as the current policy allows us to use Rhino. When/if the new licensing draft becomes policy we'll need to stop distributing Rhino and having Maven automatically downloading it. But then after 6 months/years something will be changed to resolve the issue.
  

> Resolve licensing issue with Rhino for JavaScript container
> -----------------------------------------------------------
>
>          Key: TUSCANY-44
>          URL: http://issues.apache.org/jira/browse/TUSCANY-44
>      Project: Tuscany
>         Type: Task
>   Components: Java SCA JavaScript Container
>     Reporter: Jeremy Boynes
>     Priority: Blocker

>
> The JavaScript container uses Rhino which is released under NPL1.1 - we need to resolve the licensing issues related to NPL before including this in any release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira