[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111664
]
Paul King commented on MEV-549:
-------------------------------
Take 2: Let me know if this sounds OK.
Please remove the following file as it is unusable:
maven/groovy/jars/-0.2.jar
Please update the following pom files:
http://dist.codehaus.org/groovy/poms/groovy-all-1.1-beta-1.pom ->
http://repo1.maven.org/maven/groovy/poms/groovy-all-1.1-beta-1.pom
http://dist.codehaus.org/groovy/poms/groovy-all-1.1-beta-2.pom ->
http://repo1.maven.org/maven/groovy/poms/groovy-all-1.1-beta-2.pom
(this leaves all dependencies and other info unchanged; just changes the
groupId from org.codehaus.groovy to groovy to match the directory they are in)
If this works fine, then we can look at what needs to be done for the
groovy-all and groovy-all-minimal artifacts. Thanks.
> Strange Groovy entries in the repository
> ----------------------------------------
>
> Key: MEV-549
> URL: http://jira.codehaus.org/browse/MEV-549
> Project: Maven Evangelism
> Issue Type: Task
> Components: Relocation
> Reporter: Paul King
>
> Hi, I am trying to track down why some spurious entries are showing up for
> Groovy. Please let me know if this is not the appropriate forum.
> Groovy used to publish into the maven1 repo and there was some magic in place
> that "republished" artifacts into the maven 2 repo.
> Groovy now publishes into the maven2 repo and some magic "republishes" the
> jars back into repo1.
> Unfortunately, the old magic still seems to be in place and a spurious entry
> appears (under the old groupId) in the maven 2 repo.
> Does anyone know how to turn off the old magic? I guess then we need to clean
> up the spurious artifacts but I can submit separate issue(s) for that if
> needed.
> Here is my understanding of the trail:
> (1) Project publishes to http://repository.codehaus.org/org/codehaus/groovy/
> (2) Sync happens to copy artifacts to
> http://repo1.maven.org/maven2/org/codehaus/groovy/
> (3) Magic happens here to copy artifacts back to maven 1 land ending up at
> http://repo1.maven.org/maven/groovy/jars/
> This is actually broken in that it should be being copied to
> http://repo1.maven.org/maven/org.codehaus.groovy/jars/
> and also the copying of the poms to http://repo1.maven.org/maven/groovy/poms
> (which of course should also
> be changed to http://repo1.maven.org/maven/org.codehaus.groovy/poms) has
> stopped working at some point.
> (4) Additional magic which should be turned off now occurs at this point and
> copies the artifacts back to the maven 2
> repo. An example of this from 1.1-rc-1 (12 Oct 2007) can be found here:
> http://repo1.maven.org/maven2/groovy/groovy-all/1.1-rc-1/
> This is in the wrong place given the groupId and doesn't contain a POM.
> I am trying to track this down so I can request that step (4) be turned off.
> Thanks, Paul.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
