I know, for now I at least got someone to correct the situation between central and repository.sonatype.org. They now have the same artifacts. I am also not happy about the replacement on central.
With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:50 AM, Jörg Schaible <joerg.schai...@gmx.de> wrote: > Nick Stolwijk wrote: > >> Most of the times, mirrors don't update released artifacts, because >> they should not change. So depending on your mirror you can get the >> old version. I'm already asking around on nexus irc if someone could >> resolve this issue at least for the repository.sonatype.org mirror. > > Actually it was a failure to exchange the artifact in first place. That has > always been the policy on central and this incident demonstrates exactly > why. For other known broken jars (esp. the ones containing javax. stuff) it > has always been stated, that they must release a new version. So why should > it be different in this case? You'll need junit 4.8.1-1 or the like to solve > the problem - 4.8.1 is already tainted. With all those people using local > repo managers you will never get a consistent situation anymore. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
