hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olaf Krische (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-787) groupId in deployed pom is wrong
Date Thu, 05 Aug 2010 17:17:16 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895740#action_12895740

Olaf Krische commented on ZOOKEEPER-787:


thank you for the copy, but its still not in the right location.

With groupid = "org.apache.zookeeper" and artificatid = "zookeeper", the right location is:


So it would be great to give it another try! :-)

> groupId in deployed pom is wrong
> --------------------------------
>                 Key: ZOOKEEPER-787
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-787
>             Project: Zookeeper
>          Issue Type: Bug
>    Affects Versions: 3.3.1
>            Reporter: Chris Conrad
>            Priority: Blocker
>             Fix For: 3.3.2, 3.4.0
> The pom deployed to repo1.maven.org has the project declared like this:
> <groupId>org.apache.zookeeper</groupId>
> <artifactId>zookeeper</artifactId>
> <packaging>jar</packaging>
> <version>3.3.1</version>
> But it is deployed here: http://repo2.maven.org/maven2/org/apache/hadoop/zookeeper/3.3.1
> So either the groupId needs to change or the location it is deployed to needs to be changed
because having them different results in bad behavior.  If you specify the correct groupId
in your own pom/ivy files you can't even download zookeeper because it's not where your pom
says it is and if you use the "incorrect" groupId then you can download zookeeper but then
ivy complains about:
> [error] :: problems summary ::
> [error] :::: ERRORS
> [error] 		public: bad organisation found in http://repo1.maven.org/maven2/org/apache/hadoop/zookeeper/3.3.1/zookeeper-3.3.1.pom:
expected='org.apache.hadoop' found='org.apache.zookeeper'

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message