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

Josh Rosen updated SPARK-12734:
-------------------------------
    Description: 
Netty classes are published under artifacts with different names, so our build 
needs to exclude the {{{org.jboss.netty:netty}} versions of the Netty artifact. 
However, our existing exclusions were incomplete, leading to situations where 
duplicate Netty classes would wind up on the classpath and cause compile errors 
(or worse).

We should fix this and should also start using Maven Enforcer's dependency 
banning mechanisms to prevent this problem from ever being reintroduced.

  was:
Netty classes are published under artifacts with different names, so our build 
needs to exclude the {{io.netty:netty}} and {{org.jboss.netty:netty}} versions 
of the Netty artifact. However, our existing exclusions were incomplete, 
leading to situations where duplicate Netty classes would wind up on the 
classpath and cause compile errors (or worse).

We should fix this and should also start using Maven Enforcer's dependency 
banning mechanisms to prevent this problem from ever being reintroduced.


> Fix Netty exclusions and use Maven Enforcer to prevent bug from being 
> reintroduced
> ----------------------------------------------------------------------------------
>
>                 Key: SPARK-12734
>                 URL: https://issues.apache.org/jira/browse/SPARK-12734
>             Project: Spark
>          Issue Type: Bug
>          Components: Build, Project Infra
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>             Fix For: 1.6.1, 2.0.0
>
>
> Netty classes are published under artifacts with different names, so our 
> build needs to exclude the {{{org.jboss.netty:netty}} versions of the Netty 
> artifact. However, our existing exclusions were incomplete, leading to 
> situations where duplicate Netty classes would wind up on the classpath and 
> cause compile errors (or worse).
> We should fix this and should also start using Maven Enforcer's dependency 
> banning mechanisms to prevent this problem from ever being reintroduced.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to