I've replaced the Eclipse dependencies with artifacts available from
Maven central and the Axis2 build (trunk and 1.5 branch) no longer
relies on the Eclipse repository. I will also do an attempt to
eliminate the java.net repository. If that succeeds, the build would
only use Maven central (except
On Tue, Oct 26, 2010 at 11:01, Isuru Suriarachchi wrote:
> Hi Andreas,
>
> On Tue, Oct 26, 2010 at 11:46 AM, Andreas Veithen
> wrote:
>>
>> Actually the artifacts are still in the repository (BTW, the people
>> maintaining these repos follow a very strict policy of never removing
>> any artifacts
Hi Andreas,
On Tue, Oct 26, 2010 at 11:46 AM, Andreas Veithen wrote:
> Actually the artifacts are still in the repository (BTW, the people
> maintaining these repos follow a very strict policy of never removing
> any artifacts).
I checked the above repo for the dependencies used by Axis2. For
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 expl
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
