maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <>
Subject [jira] Reopened: (MEV-549) Strange Groovy entries in the repository
Date Wed, 31 Oct 2007 07:16:04 GMT


Paul King reopened MEV-549:

We still need to do the groovy and groovy-all-minimal artifacts

> Strange Groovy entries in the repository
> ----------------------------------------
>                 Key: MEV-549
>                 URL:
>             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
> (2) Sync happens to copy artifacts to
> (3) Magic happens here to copy artifacts back to maven 1 land ending up at
> This is actually broken in that it should be being copied to
> and also the copying of the poms to (which of
course should also
> be changed to 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:
> 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:
For more information on JIRA, see:


View raw message