[
https://issues.apache.org/jira/browse/WHIRR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Crobak updated WHIRR-367:
-----------------------------
Attachment: WHIRR-367.patch
Fixes build dependencies when using artifactory as a maven proxy. The
exclusions in hama's pom.xml are only needed until HAMA-421 is resolved.
> Wrong groupId for zookeeper
> ---------------------------
>
> Key: WHIRR-367
> URL: https://issues.apache.org/jira/browse/WHIRR-367
> Project: Whirr
> Issue Type: Bug
> Components: service/hama, service/hbase, service/zookeeper
> Affects Versions: 0.5.0
> Reporter: Joe Crobak
> Labels: maven
> Attachments: WHIRR-367.patch
>
>
> The zookeeper dependency in pom.xml of several services references zookeeper
> with groupId {{org.apache.hadoop}}. This doesn't match the groupid in the
> [zookeeper-3.3.1.pom|http://repo1.maven.org/maven2/org/apache/hadoop/zookeeper/3.3.1/zookeeper-3.3.1.pom],
> which causes our proxy to return a 409 with the following in the logs:
> {noformat}
> The target deployment path
> 'org/apache/hadoop/zookeeper/3.3.1/zookeeper-3.3.1.pom' does not match the
> POM's expected path prefix 'org/apache/zookeeper/zookeeper/3.3.1'. Please
> verify your POM content for correctness and make sure the source path is a
> valid Maven 2 repository root path.
> {noformat}
> Changing the dependencies to reference groupId org.apache.zookeeper fixes the
> problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
