1.4.0RC2 and 1.4.0RC3 not available on the Maven central repo

Hi,

I’m updating our project’s pom.xml to use 1.4.0RC3 but neither it nor
RC2
are available on the Maven central repo. Any particular reason why?

Thanks,
-Mario.

HEH. Well For some reason I misread the RC3 deploy and apparently
after transferring it errored out on upload. Which is extremely odd
since I can scroll back to release and see SUCCESS printed at the end
of the deploy (so I did not look above those messages to look for an
error :slight_smile: ). I have redeployed and it seems to be there now:

http://repository.codehaus.org/org/jruby/jruby/

Thanks for bringing this up,

-Tom

On Thu, Oct 29, 2009 at 9:56 AM, Mario C. [email protected]
wrote:

Hi,
I’m updating our project’s pom.xml to use 1.4.0RC3 but neither it nor RC2
are available on the Maven central repo. Any particular reason why?
Thanks,
-Mario.


I want to change the world but they won’t give me the source code.


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Thanks Tom.

Two things:

  1. The Nexus index in http://repository.codehaus.org seems to be damaged
  2. The JRuby artifacts in the central Maven repository at
    http://repo1.maven.org/maven2/ only go up to 1.3.1.

Both of these mean that my Nexus server (our Maven proxy) can’t get
1.4.0RC[23] (1.4.0RC1 is cached, I would think from a previous download
from
the Codehaus repo).

Thanks!
-Mario.


I want to change the world but they won’t give me the source code.

I will forward this on to the folks at codehaus. Perhaps something
just got in a stuck state on their end.

-Tom

On Thu, Oct 29, 2009 at 11:05 AM, Mario C. [email protected]
wrote:

error :slight_smile: ). I have redeployed and it seems to be there now:

RC2


blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email