FYI, the cleaner has been sent in and this should now have been taken care
of.

/Anders

On Thu, May 26, 2011 at 14:41, Anders Hammar <[email protected]> wrote:

> I've also filed GRECLIPSE-1065.
>
> /Anders
>
> On Thu, May 26, 2011 at 14:33, Juven Xu <[email protected]> wrote:
>
>> these snapshots are synced from http://repository.codehaus.org:
>>
>> http://repository.codehaus.org/org/codehaus/groovy/groovy-eclipse-batch/
>> <http://repository.codehaus.org/org/codehaus/groovy/groovy-eclipse-batch/
>> >
>>
>> http://repository.codehaus.org/org/codehaus/groovy/groovy-eclipse-compiler/
>>
>> <
>> http://repository.codehaus.org/org/codehaus/groovy/groovy-eclipse-compiler/
>> >
>> @Ben
>> Is it possible that stop people deploying snapshots to this repository, or
>> even better, let groovy use http://nexus.codehaus.org/
>>
>> thanks
>>
>> On Thu, May 26, 2011 at 8:18 PM, Anders Hammar <[email protected]> wrote:
>>
>> > One thing is that project isn't using the Codehaus Nexus instance, but
>> the
>> > old maven repo...
>> >
>> > /Anders
>> >
>> > On Thu, May 26, 2011 at 13:20, Karl Heinz Marbaise <[email protected]>
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > i've got a simple question:
>> > >
>> > > How could it happen to have SNAPSHOT releases in Maven Central:
>> > >
>> > > Found by accident:
>> > >
>> >
>> http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-eclipse-compiler/
>> > >
>> > > Kind regards
>> > > Karl Heinz Marbaise
>> > >
>> > >
>> > > -----
>> > > Kind regards
>> > > Karl Heinz Marbaise
>> > > ----
>> > > http://www.soebes.de
>> > > http://www.skmwiki.de
>> > > http://supose.org/wiki/supose
>> > > --
>> > > View this message in context:
>> > >
>> >
>> http://maven.40175.n5.nabble.com/SNAPSHOT-s-in-Maven-Central-tp4428269p4428269.html
>> > > Sent from the Maven - Users mailing list archive at Nabble.com.
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: [email protected]
>> > > For additional commands, e-mail: [email protected]
>> > >
>> > >
>> >
>>
>
>

Reply via email to