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

Sean Owen updated SPARK-17422:
------------------------------
    Target Version/s: 2.0.1
            Priority: Critical  (was: Major)
         Description: Ganglia and Kinesis artifacts refer to Category 
X-licensed code. This may make them non-distributable in Maven even. We need to 
verify their status with legal.  (was: It seems that Ganglia is now BSD licensed
http://ganglia.info/ and https://sourceforge.net/p/ganglia/code/1397/

And the library we depend on for the ganglia connector has been moved to BSD 
license as well.

We should update the ganglia spark project to leverage these license changes, 
and enable it on Spark.
 )
         Component/s:     (was: Streaming)
             Summary: Verify that Ganglia, Kinesis (non-assembly) artifacts can 
be distributed.  (was: Update Ganglia project with new license)

Pardon, I'm redirecting this issue to be about the non-assembly artifacts 
(Ganglia, Kinesis), because the question is whether they can be distributed. 
Ganglia's module still does necessarily depend on a Category X license.

Marking Critical, just short of Blocker, for 2.0.1 since it may impact what we 
can distribute in a release. 

See https://issues.apache.org/jira/browse/LEGAL-198

> Verify that Ganglia, Kinesis (non-assembly) artifacts can be distributed.
> -------------------------------------------------------------------------
>
>                 Key: SPARK-17422
>                 URL: https://issues.apache.org/jira/browse/SPARK-17422
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.6.2, 2.0.0
>            Reporter: Luciano Resende
>            Priority: Critical
>
> Ganglia and Kinesis artifacts refer to Category X-licensed code. This may 
> make them non-distributable in Maven even. We need to verify their status 
> with legal.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to