[jira] Commented: (ZOOKEEPER-787) groupId in deployed pom is wrong
[ https://issues.apache.org/jira/browse/ZOOKEEPER-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898918#action_12898918 ] Olaf Krische commented on ZOOKEEPER-787: checked with 3.3.1 and works for me. thank you! 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: groupIdorg.apache.zookeeper/groupId artifactIdzookeeper/artifactId packagingjar/packaging version3.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.
[jira] Commented: (ZOOKEEPER-787) groupId in deployed pom is wrong
[ https://issues.apache.org/jira/browse/ZOOKEEPER-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896726#action_12896726 ] Brian Fox commented on ZOOKEEPER-787: - brain cramp, it's in the proper location now. 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: groupIdorg.apache.zookeeper/groupId artifactIdzookeeper/artifactId packagingjar/packaging version3.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.
[jira] Commented: (ZOOKEEPER-787) groupId in deployed pom is wrong
[ https://issues.apache.org/jira/browse/ZOOKEEPER-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895745#action_12895745 ] Alexander Warschun commented on ZOOKEEPER-787: -- would also like to see this fixed, maybe with another move to path /org/apache. thx a lot 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: groupIdorg.apache.zookeeper/groupId artifactIdzookeeper/artifactId packagingjar/packaging version3.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.
[jira] Commented: (ZOOKEEPER-787) groupId in deployed pom is wrong
[ https://issues.apache.org/jira/browse/ZOOKEEPER-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895118#action_12895118 ] Brian Fox commented on ZOOKEEPER-787: - Since the poms were correct and the deployed location simply wrong, I copied the artifacts to the correct path which is org/apache/zookeeper. Give it a few hours to sync to central. 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: groupIdorg.apache.zookeeper/groupId artifactIdzookeeper/artifactId packagingjar/packaging version3.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.
