On Wed, Dec 29, 2010 at 09:25, Afkham Azeez <[email protected]> wrote: > > > On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <[email protected]> > wrote: >> >> There is another issue with that release caused by the change in >> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The >> problem is that this repository is not properly managed. It contains >> artifacts with the same groupId, artifactId and version as Maven >> central, but with different content. Example: >> >> >> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom >> >> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom > > Can you please enlighten us on how you detected these discrepancies, and > also let us know what else seems to be out of order in > the http://dist.wso2.org/maven2 repo?
That was by pure coincidence. I noticed that when building the Sandesha2 1.4 branch with an empty local repository, at some point, Maven started downloading things with -wso2vX in the version number. I've been able to track this down to the discrepancy in addressing-1.5.pom. Note that Sandesha2 1.4 doesn't use the WSO2 repository, but depends on Rampart 1.5 which uses it. I did some changes (usage of dependencyManagement) to the Sandesha2 build to work around this issue, but you can still reproduce it with the 1.4 tag. You can also reproduce this with the last Synapse 2.0 release candidate. Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
