You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Bowen Zhang (JIRA)" <ji...@apache.org> on 2013/01/28 23:41:13 UTC

[jira] [Updated] (OOZIE-1193) upgrade jython to 2.5.3 for Pig in Oozie due to jython 2.5.0 legal issues

     [ https://issues.apache.org/jira/browse/OOZIE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bowen Zhang updated OOZIE-1193:
-------------------------------

    Description: 

Jython 2.5.0 redistributes an external LGPL component (JNA) in a manner that puts Jython out of compliance with the LGPL. As such dependent components like Pig and Oozie are also arguably out of compliance with the LGPL.

It appears that this has been quietly found and fixed by the Jython guys, as version 2.5.3 does not include the JNA component. However the status of 2.5.0 with respect to the LGPL and Apache legal is still unclear.

The easiest way to remediate this whole problem is to simply move Pig and Oozie to Jython 2.5.3 and remove the question.

    
> upgrade jython to 2.5.3 for Pig in Oozie due to jython 2.5.0 legal issues
> -------------------------------------------------------------------------
>
>                 Key: OOZIE-1193
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1193
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Bowen Zhang
>            Assignee: Bowen Zhang
>
> Jython 2.5.0 redistributes an external LGPL component (JNA) in a manner that puts Jython out of compliance with the LGPL. As such dependent components like Pig and Oozie are also arguably out of compliance with the LGPL.
> It appears that this has been quietly found and fixed by the Jython guys, as version 2.5.3 does not include the JNA component. However the status of 2.5.0 with respect to the LGPL and Apache legal is still unclear.
> The easiest way to remediate this whole problem is to simply move Pig and Oozie to Jython 2.5.3 and remove the question.

--
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: http://www.atlassian.com/software/jira