Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Wayne Fay
> 1) the reporter of the ticket attached a broken junit artifact
> 2) I uploaded it into central without checking the internal of the jar
> 3) Paul 
> Kingfound
> it's broken and notified me
> 4) I fixed the broken junit in central
>
> so the broken junit 4.8.1 did exist in central for about 6 hours :(

So is the new policy to fix broken artifacts, or leave them broken?
IMO they must remain broken and version-bumped to deploy fixes.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Juven Xu
I just fixed the repository.sonatype.org mirror.

>From the ticket http://jira.codehaus.org/browse/MAVENUPLOAD-2695 you can see
why this happened:

1) the reporter of the ticket attached a broken junit artifact
2) I uploaded it into central without checking the internal of the jar
3) Paul 
Kingfound
it's broken and notified me
4) I fixed the broken junit in central

so the broken junit 4.8.1 did exist in central for about 6 hours :(

this explains why we ask pgp signatures for artifacts which wants to be
synced.

On Wed, Apr 28, 2010 at 5:27 PM, 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.
>
> 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 
> wrote:
> > Le Wed, 28 Apr 2010 11:07:02 +0200,
> > Nick Stolwijk  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 
> wrote:
> >> > Le Wed, 28 Apr 2010 10:52:48 +0200,
> >> > Nick Stolwijk  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 
> 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  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
> >> >> >>> > 
> >> >> >>> >junit
> >> >> >>> >junit
> >> >> >>> >4.8.1
> >> >> >>> >test
> >> >> >>> > 
> >> >> >>> >
> >> >> >>> > 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: users-unsubscr...@maven.apache.org
> >> >> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >> >> >>>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Tony Chemit
> >> >> >> 
> >> >> >> tél: +33 (0) 2 40 50 29 28
> >> >> >> email: che...@codelutin.com
> >> >> >> http://www.codelutin.com
> >> >> >>
> >> >> >>
> -
> >> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >> >> For additional commands, e-mail: users-h...@maven.apache.org
> >> >> >>
> >> >> >>
> >> >> >>

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
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  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



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Jörg Schaible
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



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
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  wrote:
> Le Wed, 28 Apr 2010 11:07:02 +0200,
> Nick Stolwijk  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  wrote:
>> > Le Wed, 28 Apr 2010 10:52:48 +0200,
>> > Nick Stolwijk  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  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  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
>> >> >>> > 
>> >> >>> >    junit
>> >> >>> >    junit
>> >> >>> >    4.8.1
>> >> >>> >    test
>> >> >>> > 
>> >> >>> >
>> >> >>> > 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: users-unsubscr...@maven.apache.org
>> >> >>> For additional commands, e-mail: users-h...@maven.apache.org
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Tony Chemit
>> >> >> 
>> >> >> tél: +33 (0) 2 40 50 29 28
>> >> >> email: che...@codelutin.com
>> >> >> http://www.codelutin.com
>> >> >>
>> >> >> -
>> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> > --
>> >> > 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: 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
>> >>
>> >
>> >
>> >
>> > --
>> > Tony Chemit
>> > 
>> > tél: +33 (0) 2 40 50 29 28
>> > email: che...@codelutin.com
>> > http://www.codelutin.com
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@mav

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Tony Chemit
Le Wed, 28 Apr 2010 11:07:02 +0200,
Nick Stolwijk  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  wrote:
> > Le Wed, 28 Apr 2010 10:52:48 +0200,
> > Nick Stolwijk  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  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  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
> >> >>> > 
> >> >>> >    junit
> >> >>> >    junit
> >> >>> >    4.8.1
> >> >>> >    test
> >> >>> > 
> >> >>> >
> >> >>> > 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: users-unsubscr...@maven.apache.org
> >> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Tony Chemit
> >> >> 
> >> >> tél: +33 (0) 2 40 50 29 28
> >> >> email: che...@codelutin.com
> >> >> http://www.codelutin.com
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>
> >> >>
> >> >>
> >> >
> >> > --
> >> > 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: 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
> >>
> >
> >
> >
> > --
> > Tony Chemit
> > 
> > tél: +33 (0) 2 40 50 29 28
> > email: che...@codelutin.com
> > http://www.codelutin.com
> >
> > -
> > 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
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
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.

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  wrote:
> Le Wed, 28 Apr 2010 10:52:48 +0200,
> Nick Stolwijk  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  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  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
>> >>> > 
>> >>> >    junit
>> >>> >    junit
>> >>> >    4.8.1
>> >>> >    test
>> >>> > 
>> >>> >
>> >>> > 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: users-unsubscr...@maven.apache.org
>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Tony Chemit
>> >> 
>> >> tél: +33 (0) 2 40 50 29 28
>> >> email: che...@codelutin.com
>> >> http://www.codelutin.com
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >>
>> >>
>> >>
>> >
>> > --
>> > 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: 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
>>
>
>
>
> --
> Tony Chemit
> 
> tél: +33 (0) 2 40 50 29 28
> email: che...@codelutin.com
> http://www.codelutin.com
>
> -
> 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



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Tony Chemit
Le Wed, 28 Apr 2010 10:52:48 +0200,
Nick Stolwijk  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  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  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
> >>> > 
> >>> >    junit
> >>> >    junit
> >>> >    4.8.1
> >>> >    test
> >>> > 
> >>> >
> >>> > 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: users-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> Tony Chemit
> >> 
> >> tél: +33 (0) 2 40 50 29 28
> >> email: che...@codelutin.com
> >> http://www.codelutin.com
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >>
> >
> > --
> > 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: 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
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
It seems there has been a faulty upload [1] but it was fixed later.
For example, [2] has the "right" version of junit 4.8.1. I wouldn't
trust this release with maven. Based on your mirror you can get the
borked version.

[1] 
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs
[2] http://mirrors.ibiblio.org/pub/mirrors/maven2/junit/junit/4.8.1/

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:52 AM, Nick Stolwijk  wrote:
> 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.
>
> 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  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  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
 > 
 >    junit
 >    junit
 >    4.8.1
 >    test
 > 
 >
 > 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: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

>>>
>>>
>>>
>>> --
>>> Tony Chemit
>>> 
>>> tél: +33 (0) 2 40 50 29 28
>>> email: che...@codelutin.com
>>> http://www.codelutin.com
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>>
>> --
>> 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: 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



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
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.

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  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  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
>>> > 
>>> >    junit
>>> >    junit
>>> >    4.8.1
>>> >    test
>>> > 
>>> >
>>> > 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: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>
>>
>>
>> --
>> Tony Chemit
>> 
>> tél: +33 (0) 2 40 50 29 28
>> email: che...@codelutin.com
>> http://www.codelutin.com
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>
> --
> 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: 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



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread ykyuen

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  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
>> > 
>> >junit
>> >junit
>> >4.8.1
>> >test
>> > 
>> > 
>> > 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: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
> 
> 
> 
> -- 
> Tony Chemit
> 
> tél: +33 (0) 2 40 50 29 28
> email: che...@codelutin.com  
> http://www.codelutin.com 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Tony Chemit
Le Wed, 28 Apr 2010 09:59:05 +0200,
Dirk Olmes  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
> > 
> >junit
> >junit
> >4.8.1
> >test
> > 
> > 
> > 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: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Raphael Ackermann
But it is available in central.

http://repository.sonatype.org/index.html#nexus-search;gav~~junit~4.8.1~~

we have been using it for at least a week now.

Raphael

On Wed, Apr 28, 2010 at 09:59, Dirk Olmes  wrote:
> 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
>> 
>>    junit
>>    junit
>>    4.8.1
>>    test
>> 
>>
>> 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?
>
> No, it's just that JUnit 4.8.1 isn't available in the central repo (for
> now).
>
> -dirk
>
> -
> 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



Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Dirk Olmes
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
> 
>junit
>junit
>4.8.1
>test
> 
> 
> 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?

No, it's just that JUnit 4.8.1 isn't available in the central repo (for
now).

-dirk

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org