[ http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111926 ]
Paul King commented on MEV-549: ------------------------------- 1.1-beta-1 was a change in decision about case in naming the release but 1.1-BETA-1 was already pushed to the repo so for repo stability we should just make both available. The jar can just be copied and renamed. Obviously the BETA-1 pom should have the uppercase artifactId inside it. Re: the comment in MEV-550: http://repo1.maven.org/maven2/groovy/groovy-all/1.0/groovy-all-1.0.pom still contains the unchanged reference to openejb http://dist.codehaus.org/groovy/poms/groovy-all-1.0.pom contains the exclusion of the problem castor dependency and points to the non-snapshot dependency. If that could be copied across, that would be great. Thanks, Paul. > 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