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.
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:21 AM, Tony Chemit <[email protected]> wrote: > Le Wed, 28 Apr 2010 11:07:02 +0200, > Nick Stolwijk <[email protected]> a écrit : > >> That depends on where you look. ;) >> >> Take a look at >> http://repository.sonatype.org/index.html#nexus-search;gav~~junit~4.8.1~~ >> >> That one certainly is borked. See also the jira issue in my other >> mail. There are different versions of this artifact in >> central/mirrors. As long as not all mirrors purge their old version, I >> wouldn't trust this version. Normally, central had a very strict >> policy, what is on central, stays on central, but it seems someone >> slipped this time. >> > Ok I tought that only http://repo1.maven.org/maven2/ was central, and mirrors > could be cleaned. (but still respects the policy of 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:01 AM, Tony Chemit <[email protected]> wrote: >> > Le Wed, 28 Apr 2010 10:52:48 +0200, >> > Nick Stolwijk <[email protected]> a écrit : >> > >> >> It seems the 4.8.1 version in central is borked. It doesn't contain >> >> any classes. That would explain why your imports can't be resolved. I >> >> don't know who did the upload of this artifact, but it is certainly >> >> wrong. >> > Nope, there is some classes inside the jar. >> > >> > For me there is nothing wrong with the artifact 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 10:22 AM, ykyuen <[email protected]> wrote: >> >> > >> >> > Yes. i can see the junit-4.8.1.jar in "Maven Dependencies" of my eclipse >> >> > project. so i am sure the maven did download the 4.8.1 jar. >> >> > >> >> > >> >> > >> >> > Tony Chemit wrote: >> >> >> >> >> >> Le Wed, 28 Apr 2010 09:59:05 +0200, >> >> >> Dirk Olmes <[email protected]> a écrit : >> >> >> >> >> >>> On 04/28/2010 08:46 AM, ykyuen wrote: >> >> >>> > >> >> >>> > i try to use junit 4.8.1 in my maven project by adding the following >> >> >>> > dependency in the pom.xml >> >> >>> > <dependency> >> >> >>> > <groupId>junit</groupId> >> >> >>> > <artifactId>junit</artifactId> >> >> >>> > <version>4.8.1</version> >> >> >>> > <scope>test</scope> >> >> >>> > </dependency> >> >> >>> > >> >> >>> > when i try to write the test case, the org.junit cannot be >> >> >>> resolved(i.e. >> >> >>> > error at "import org.junit.Assert"). but if i change the junit >> >> >>> > version >> >> >>> to >> >> >>> > 4.7. no problem at all. >> >> >>> > >> >> >>> > did i do anything wrong? >> >> >> When you have this error, is it in a IDEA ? or when you launch a maven >> >> >> build ? >> >> >> >> >> >>> >> >> >>> No, it's just that JUnit 4.8.1 isn't available in the central repo >> >> >>> (for >> >> >>> now). >> >> >> >> >> >> I can see it on central here : >> >> >> >> >> >> http://repo1.maven.org/maven2/junit/junit/4.8.1/ >> >> >> >> >> >>> >> >> >>> -dirk >> >> >>> >> >> >>> --------------------------------------------------------------------- >> >> >>> To unsubscribe, e-mail: [email protected] >> >> >>> For additional commands, e-mail: [email protected] >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Tony Chemit >> >> >> -------------------- >> >> >> tél: +33 (0) 2 40 50 29 28 >> >> >> email: [email protected] >> >> >> http://www.codelutin.com >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: [email protected] >> >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> >> >> >> >> >> >> > >> >> > -- >> >> > View this message in context: >> >> > http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.html >> >> > Sent from the Maven - Users mailing list archive at Nabble.com. >> >> > >> >> > >> >> > --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: [email protected] >> >> > For additional commands, e-mail: [email protected] >> >> > >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> > >> > >> > >> > -- >> > Tony Chemit >> > -------------------- >> > tél: +33 (0) 2 40 50 29 28 >> > email: [email protected] >> > http://www.codelutin.com >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Tony Chemit > -------------------- > tél: +33 (0) 2 40 50 29 28 > email: [email protected] > http://www.codelutin.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
