Actually the artifacts are still in the repository (BTW, the people maintaining these repos follow a very strict policy of never removing any artifacts). However, for some reasons, Maven attempts to resolve some of the dependencies from central (and only from central). For the moment I have no explanation for this. Note that this is not necessarily a problem with the Eclipse repo, but could be caused by artifacts added to one of the other repositories we use. The really annoying thing is that the issue also occurs on the 1.5 branch, and therefore probably also with the 1.5.2 sources. This means that after the java.net incident, we again ended up in a situation where our previous releases are no longer buildable.
Interestingly, when using Maven 3.0 (beta 1), the build actually succeeds... Andreas On Mon, Oct 25, 2010 at 14:40, Isuru Suriarachchi <isur...@gmail.com> wrote: > Hi all, > > Our axis2-eclipse plugins use few eclipse dependencies and their current > version is 3.2.0. And the eclipse maven repository we are using is [1]. But > version 3.2.0 of those dependencies are no longer available in [1]. So when > we build axis2 with a clean repository, it breaks. > > So how are we going to fix this? Are there any other maven repository with > eclipse libraries? > > Thanks, > ~Isuru > > [1] http://repo1.maven.org/eclipse > > -- > Technical Lead, > WSO2 Inc. http://wso2.org/ > Blog : http://isurues.wordpress.com/ > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
