> - javax.xml.ws:jaxws-api:2.1 (has dependencies in dev.java.net that are NOT
DON'T use this one. The jar at central is not really "correct". It was at one point, but then Sun decided to withdraw it and then re-release it at java.net. Since central won't remove or change things, the one at central is different than the one at java.net. Make sure you use 2.1-1 which will pull from central in all cases. Basically, I highly suggest not ever relying on anything from java.net. They have a nasty tendency to re-release new versions of things, but with the same version number. Thus, builds will randomly break and such. It really gets confusing in the cases where the artifact HAD been synced to central. The jaxws-api:2.1 jar is one example. It was synced to central, then Sun re- relased it. saaj-impl:1.3 is another example. Sun put a new version (that wasn't completely compatible) on java.net and suddenly my builds started breaking after I cleaned my local repo. Developers that didn't have clean repos were OK. Frustrating to track down and was kind of the "final staw" when I decided not to have java.net repo dependencies in my builds anymore. Dan On Wed September 23 2009 3:04:41 pm Roland Asmann wrote: > Hi all, > > I don't know who's responsible, so I hope I'm posting this at the right > place... I'm switching my company to Nexus, and happened upon a couple of > problems. > > As far as I can see, the reason for this is as follows: > - Originally I had the 2 dev.java.net repositories in my POM, which made > Maven check those BEFORE it checked repo1.maven.org > - Nexus advises to set the order of your repositories so that the most > likely one to have a 'hit' be the first in the list --> this would > normally be repo1.maven.org > > Now, since there are a couple of differences between several artifacts, I > am no longer able to build all of my projects! > > The question is, should this be changed in repo1.maven.org and who can do > this? For now, I can just reconfigure Nexus to check dev.java.net first, > but that's not the correct solution. > > The artifacts that give me problems are: > - javax.xml.soap:saaj-api:1.3 (dependency to activation is different) > - javax.xml.ws:jaxws-api:2.1 (has dependencies in dev.java.net that are NOT > in repo1.maven.org) > > Also there are some differences in other artifacts that are no problem to > the build (licenses, repositories), but it might be a good idea to sync > those as well... > > So, if I'm not supposed to post this here, I'm sorry --> please direct me > to the right place. Otherwise I hope someone can look into this problem > and fix it! > -- Daniel Kulp [email protected] http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
