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

2016-01-11 Thread Apache Spark (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092616#comment-15092616
 ] 

Apache Spark commented on SPARK-12734:
--

User 'JoshRosen' has created a pull request for this issue:
https://github.com/apache/spark/pull/10704

> 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.5.3, 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

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

2016-01-10 Thread Apache Spark (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091538#comment-15091538
 ] 

Apache Spark commented on SPARK-12734:
--

User 'JoshRosen' has created a pull request for this issue:
https://github.com/apache/spark/pull/10693

> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

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

2016-01-10 Thread Apache Spark (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091425#comment-15091425
 ] 

Apache Spark commented on SPARK-12734:
--

User 'JoshRosen' has created a pull request for this issue:
https://github.com/apache/spark/pull/10691

> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

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

2016-01-10 Thread Apache Spark (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091420#comment-15091420
 ] 

Apache Spark commented on SPARK-12734:
--

User 'JoshRosen' has created a pull request for this issue:
https://github.com/apache/spark/pull/10690

> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

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

2016-01-08 Thread Apache Spark (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090453#comment-15090453
 ] 

Apache Spark commented on SPARK-12734:
--

User 'JoshRosen' has created a pull request for this issue:
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
>
> Netty classes are published under artifacts with different names, so our 
> build needs to exclude the {{io.netty}} and {{org.jboss.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