www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Sanchez <car...@apache.org>
Subject Re: Removing an accidental release from the central
Date Sat, 07 Feb 2009 06:03:37 GMT
another thing you have to consider is that it also got propagated to
the mirrors. What would be the problem leaving it there? are you
making a new release any time soon?

I think the Maven project parent pom has a staging repo defined. It
may be useful to move that up to the apache parent pom


On Fri, Feb 6, 2009 at 3:54 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
>
> I just found an accidentally deployed Jackrabbit artifact on the
> central repository, see [1]. This is not an official Jackrabbit
> release and was removed from the m2-ibiblio-rsync-repository on p.a.o
> shortly after it was accidentally deployed there last year.
> Unfortunately it looks like the artifact got synchronized to central
> before it was removed.
>
> Is there a way to remove the jackrabbit-spi2dav_ex directory from
> central? This release has not been advertised anywhere and I would be
> quite surprised if anyone was using it for anything.
>
> On a related note, is it a good idea to have the apache.releases
> repository configured in the Apache parent POM? This setting makes an
> accidental "mvn deploy" on a non-snapshot tree deploy things directly
> to the m2-ibiblio-rsync-repository. It would be safer if the
> deployment repository was either not configured at all, or pointed to
> some staging repository like the new Nexus server that's being set up
> for Apache.
>
> [1] http://repo2.maven.org/maven2/org/apache/jackrabbit/jackrabbit-spi2dav_ex/1.5-R42198/
>
> BR,
>
> Jukka Zitting
>

Mime
View raw message