[jira] [Resolved] (SPARK-12734) Fix Netty exclusions and use Maven Enforcer to prevent bug from being reintroduced

["Josh Rosen (JIRA)" <ji...@apache.org>]

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

Josh Rosen resolved SPARK-12734.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request 10672
[https://github.com/apache/spark/pull/10672]

> 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: 2.0.0
>
>
> 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.



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

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