synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Build failures caused by old snapshots in WSO2 repository
Date Mon, 27 Sep 2010 12:18:37 GMT

When building Synapse with a clean local Maven repository, I'm getting
the following type of error:

1) org.apache.axis2:axis2-transport-base:jar:1.1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.apache.axis2
-DartifactId=axis2-transport-base -Dversion=1.1.0-20100122.094109-5
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=org.apache.axis2
-DartifactId=axis2-transport-base -Dversion=1.1.0-20100122.094109-5
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  	1) org.apache.synapse:synapse-distribution:pom:2.1.0-SNAPSHOT
  	2) org.apache.synapse:synapse-vfs-transport:jar:2.1.0-SNAPSHOT
  	3) org.apache.axis2:axis2-transport-base:jar:1.1.0-SNAPSHOT

I believe that the root cause is that Nexus (
doesn't maintain the maven-metadata.xml file in a correct way and that
Maven tends to be confused by timestamped snapshots. However, the
issue only occurs because the WSO2 repository
( also contains snapshots of
Apache projects (Axis2, Axis2 transports, Rampart and Sandesha).
Because of the Nexus issue, Maven believes that these snapshots are
more recent, but then fails to download them because at some point it
attempts to fetch them from the release repositories (because of the

Anyway, since the snapshots in the WSO2 repository are completely
outdated and we now have regular snapshot deployments to Nexus, would
it be possible to remove the snapshots from the WSO2 repository?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message