maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MEV-549) Strange Groovy entries in the repository
Date Tue, 30 Oct 2007 22:26:04 GMT

    [ http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112148
] 

Carlos Sanchez commented on MEV-549:
------------------------------------

i wouldn't worry about maven 1 as it doesn't need the poms

> 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
>            Assignee: Carlos Sanchez
>
> 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

        

Mime
View raw message