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

Sean Busbey commented on HADOOP-13922:
--------------------------------------

Yeah. The dev commentary on [extra-enforcer-rules 
#13|https://github.com/mojohaus/extra-enforcer-rules/issues/13] also left me 
with little confidence in the overall maven ecosystem's ability to cope with 
pom dependencies, which has been an issue even for inter-module dependencies 
within HBase (HBASE-17286).

Thanks for checking the fix [~jpallas]!

I think this is ready to go.

> Some modules have dependencies on hadoop-client jar removed by HADOOP-11804
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-13922
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13922
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Joe Pallas
>            Assignee: Sean Busbey
>            Priority: Blocker
>         Attachments: HADOOP-13922.1.patch
>
>
> As discussed in [HADOOP-11804 comment 
> 15758048|https://issues.apache.org/jira/browse/HADOOP-11804?focusedCommentId=15758048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15758048]
>  and following comments, there are still dependencies on the now-removed 
> hadoop-client jar.  The current code builds only because an obsolete snapshot 
> of the jar is found on the repository server.  Changing the project version 
> to something new exposes the problem.
> While the build currently dies at hadoop-tools/hadoop-sls, I'm seeing issues 
> with some Hadoop Client modules, too.
> I'm filing a new bug because I can't reopen HADOOP-11804.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to