You have managed to deploy a snapshot to central

Apologies for that. Any way to remove the snapshot from maven central?

I'll switch to the nexus instance. Is there any documentation for this explaining exactly what I should and should not be doing? I am new to maven as well as maven deployment and so I wasn't aware of these restrictions and conventions.

I found this:
http://docs.codehaus.org/display/HAUSMATES/Codehaus+Maven+Repository+Usage+Guide

I will delete the snapshots from the codehaus repository that is synced to maven, but still not sure how to delete from maven.

I will delete them from maven central

Thanks Juven.

Two more snapshots made it over to central:
http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-eclipse-batch/1.7.10-SNAPSHOT/
http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-eclipse-batch/1.8.0-SNAPSHOT-02/

these snapshots are deleted from central, you can close this ticket now

Andrew,

the docs for switching to the Nexus instance is here:
http://docs.codehaus.org/display/HAUSMATES/Codehaus+Maven+Repository+Usage+Guide

Juven will help you when you've created the appropriate jira ticket.

Btw, thanks for taking this seriously and acting!

Thanks for helping me out here and for helping me figure out what I should be doing.

Is there any chance that you can fix the metadata on central for these artifacts? If I look at the maven-metadata-central.xml that gets copied into my local repository, it has the following:

<?xml version="1.0" encoding="UTF-8"?>

<metadata>
  <groupId>org.codehaus.groovy</groupId>
  <artifactId>groovy-eclipse-batch</artifactId>
  <versioning>
    <latest>1.8.0-03</latest>
    <release>1.8.0-03</release>
    <versions>
      <version>1.7.10-SNAPSHOT</version>
      <version>1.7.10-01</version>
      <version>1.7.10-02</version>
      <version>1.8.0-SNAPSHOT-02</version>
      <version>1.8.0-01</version>
      <version>1.8.0-02</version>
      <version>1.8.0-03</version>
    </versions>
    <lastUpdated>20110527175716</lastUpdated>
  </versioning>
</metadata>

You can see that it still lists the SNAPSHOTS. I'm using Maven 2.0.11, and whenever I use groovy-eclipse-compiler which has a version-range dependency on groovy-eclipse-batch, it tries to download 1.8.0-SNAPSHOT-02 (I have no idea why). I can add an explicit dependency to the correct version of groovy-eclipse-batch, but it still insists on trying to download version 1.8.0-SNAPSHOT-02. When it doesn't find it, it carries on and the build works, but it still adds a few seconds delay every time I compile the project...

Thanks, Alex.

That's annoying. I'll see what I can do.

These SNAPSHOT versions don't exist, but the metadata at central say they exist. The way to get this fixed is to file a ticket at
https://issues.sonatype.org/browse/MVNCENTRAL

Already done:
https://issues.sonatype.org/browse/MVNCENTRAL-97

Waiting to hear back.