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

Cheolsoo Park commented on PIG-3905:
------------------------------------

I think this is a valid bug. Even though the build doesn't fail for me (because 
hadoop-core-1.0.0.jar is found in maven repo), hadoop20 and hadoop23 confs are 
always resolved regardless hadoopversion-
{code}
[ivy:resolve] :: resolving dependencies :: org.apache.pig#pig;0.12.2-SNAPSHOT
[ivy:resolve]   confs: [master, default, runtime, compile, test, javadoc, 
releaseaudit, jdiff, checkstyle, buildJar, hadoop20, hadoop23, hbase94, hbase95]
{code}
This seems wrong to me.

For example, sqoop only resolves one hadoop conf specified by hadoopversion- 
{code}
[ivy:resolve] :: resolving dependencies :: 
com.cloudera.sqoop#sqoop;working@lgml-cheolsoop
[ivy:resolve]   confs: [hadoop20]
{code}

We should fix this. I don't have an explanation why this becomes an issue in 
0.12.1 because it has existed since the beginning.

> 0.12.1 release can't be build for Hadoop2
> -----------------------------------------
>
>                 Key: PIG-3905
>                 URL: https://issues.apache.org/jira/browse/PIG-3905
>             Project: Pig
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.12.1
>            Reporter: Konstantin Boudnik
>            Priority: Blocker
>
> While building Pig against {{hadoopversion=23}},  attempts to resolve 
> {{hadoop-core}} dependency no matter what. The root cause of the bug is the 
> following lines in ivy.xml
> {noformat}
>     <dependency org="com.sun.jersey" name="jersey-core" 
> rev="${jersey-core.version}"
>       conf="hadoop20->default"/>
>     <dependency org="org.apache.hadoop" name="hadoop-core" 
> rev="${hadoop-core.version}"
>       conf="hadoop20->default"/>
>     <dependency org="org.apache.hadoop" name="hadoop-test" 
> rev="${hadoop-test.version}"
>       conf="hadoop20->default"/>
> {noformat}
> hadoop20 configuration is getting evaluated _always_. Unless a build machine 
> has dirty local .m2 repository, the build will fail.
> The bug blocks BIGTOP-1110



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to