You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Joe Crobak (JIRA)" <ji...@apache.org> on 2011/08/16 16:21:27 UTC
[jira] [Created] (WHIRR-367) Wrong groupId for zookeeper
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
Reporter: Joe Crobak
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
[jira] [Updated] (WHIRR-367) Wrong groupId for zookeeper
Posted by "Joe Crobak (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (WHIRR-367) Wrong groupId for zookeeper
Posted by "Joe Crobak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088197#comment-13088197 ]
Joe Crobak commented on WHIRR-367:
----------------------------------
To pickup the hama fixes, the hama version will have to be bumped to 0.4.0-incubating-SNAPSHOT. Is that acceptable?
> 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
[jira] [Commented] (WHIRR-367) Wrong groupId for zookeeper
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088132#comment-13088132 ]
Tom White commented on WHIRR-367:
---------------------------------
+1 Looks good to me. The Hama issue has been resolved, so can the patch be simplified now?
> 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
[jira] [Updated] (WHIRR-367) Wrong groupId for zookeeper
Posted by "Joe Crobak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Crobak updated WHIRR-367:
-----------------------------
Affects Version/s: 0.5.0
Status: Patch Available (was: Open)
> 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