On 10 October 2011 01:31, Gary Gregory <[email protected]> wrote: > On Sun, Oct 9, 2011 at 8:07 PM, sebb <[email protected]> wrote: > >> On 9 October 2011 18:41, Gary Gregory <[email protected]> wrote: >> > I am inching toward success... >> > >> > Friday, I released 2.1 to repository.apache.org and I can see it: >> > https://repository.apache.org/index.html#nexus-search;quick~commons-io >> > >> > I am confused by what is on Maven Central: >> > http://search.maven.org/#search%7Cga%7C1%7Ccommons-io >> >> The first line also says "all (12)" - click that link, and you see all >> the versions. >> >> > No 2.0, no 2.0.1, no 2.1 >> > >> > But it is here: http://repo1.maven.org/maven2/commons-io/commons-io/ >> >> That's correct, apart from the directory >> >> http://repo1.maven.org/maven2/commons-io/commons-io/20030203.000550/ >> >> which is rather odd; I don't see why that should be there. >> >> Looks like a snapshot version got lost and ended up in the wrong repo. >> >> > Uh? >> >> I'll raise a bug report with Central. >> >> > Recent commons-codec releases do not even show up when you do a MC >> "search". >> >> Yes, they do - see "all (6)" - same problem as with commons-io. >> >> I'll raise another issue.
Raised: (MVNCENTRAL-126) Spurious entry in commons-io (MVNCENTRAL-127) Spurious entry in commons-codec Then I noticed that loads of commons directories have been affected, so I raised (MVNCENTRAL-128) Huge mess in commons directories Looks like something went horribly wrong at 04-Jan-2007 19:17 because all the spurious entries I have seen are dated then. MVNCENTRAL-126 has already been closed as Won't FIx (usual mantra about not being able to change anything that has been published), but in this case it looks as though the publishing was not intentional, so I hope they will actually clear up the mess. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
