> already downloaded apache-3.pom the build continues without any trouble. But
> I think the problem here is that as I use the Axis2 1.4.1 version and not
> the newest snapshot and the 1.4.1 version is already in the repo so the
> change should be made there, no? Isn't this issue affecting anybody
Hi,
first of all thanks for your time and effort. Indeed, the problem is
the repository entry (https://maven-repository.dev.java.net/nonav/repository/
) in the axis2-parent.pom. If I change it correspondingly and remove
the already downloaded apache-3.pom the build continues without any
tr
Martin,
I have fixed this in Axis2 trunk and you can get an svn up and simply build
now.
Lahiru
On Thu, Nov 12, 2009 at 7:34 PM, Martin Scholl <
martin.sch...@enviromatics.net> wrote:
> Hi all,
>
> I'm trying to build/clean a multi-module project where one of the modules
> uses the Axis2 mar pl
Hi Martin,
Please change the modules/parent/pom.xml in Axis2 like this.
Remove the java.net repository from your pom.xml and add the new location ,
like this.
---
-
+
+
+java.net
+http://download.java.net/maven/1
+legacy
+
+
Strange, all related poms seems to exist at central:
http://repo1.maven.org/maven2/org/apache/axis2/axis2-parent/1.4.1/axis2-parent-1.4.1.pom
http://repo1.maven.org/maven2/org/apache/apache/3/apache-3.pom
Try deleting your local repo (or related parts of it) and then execute build
again.
/Anders
Hi all,
I'm trying to build/clean a multi-module project where one of the
modules uses the Axis2 mar plugin. During build/clean maven tries to
download the org.apache:apache:pom:3 from the repo. Maven finds the
file but it contains HTML that states "301 moved permanently". This
causes the
