You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Julien Le Dem (JIRA)" <ji...@apache.org> on 2012/09/28 20:11:08 UTC

[jira] [Commented] (PIG-2938) All unit tests that use MR2 MiniCluster are broken in trunk

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

Julien Le Dem commented on PIG-2938:
------------------------------------

Sorry I broke the hadoop23 build.
This looks like a hadoop 23 runtime dependency, it should be in the hadoop23 configuration in ivy.xml
any reason it is not pulled automatically?
                
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
>                 Key: PIG-2938
>                 URL: https://issues.apache.org/jira/browse/PIG-2938
>             Project: Pig
>          Issue Type: Bug
>          Components: build
>            Reporter: Cheolsoo Park
>            Assignee: Cheolsoo Park
>            Priority: Critical
>         Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.

--
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