groupId in deployed pom is wrong
Issue Type: Bug
Affects Versions: 3.3.1
Reporter: Chris Conrad
The pom deployed to repo1.maven.org has the project declared like this:
But it is deployed here:
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
[error] :: problems summary ::
[error] :::: ERRORS
[error] public: bad organisation found in
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.