My coworker just found out that version 2.0 of surefire shows the correct
error msgs.So it seems that error handling was changed between them and now
it swallows the correct exceptions :-/
That would have saved a lot of time debugging this lol.
On Wed, Apr 8, 2009 at 7:45 AM, Tim wrote:
> That's
That's good to know :)
I can double check but that is probably not what is happening here since it
is defined in the parent pom as junit 4.
On Wed, Apr 8, 2009 at 7:15 AM, Jörg Schaible wrote:
> Hi Tim,
>
> Tim wrote at Mittwoch, 8. April 2009 14:05:
>
> > Unfortunately not. It seems however tha
Hi Tim,
Tim wrote at Mittwoch, 8. April 2009 14:05:
> Unfortunately not. It seems however that surefire is actually giving the
> wrong stacktrace.
> When I run this via the cli using the classpath that surefire says it is
> using I get a different exception.
> It seems that a dependency was missi
Unfortunately not. It seems however that surefire is actually giving the
wrong stacktrace.
When I run this via the cli using the classpath that surefire says it is
using I get a different exception.
It seems that a dependency was missing at that point. When I added it, I got
a new exception instead
Is there more of a trace supplied from within Surefire? Have you
searched to see if anyone else encountered this problem?
Thanks,
Brett
On 08/04/2009, at 10:47 AM, Tim wrote:
yea the tmp files look fine. In fact I see the correct junit jar
version and
all the dependency jars correctly in t
yea the tmp files look fine. In fact I see the correct junit jar version and
all the dependency jars correctly in them.Still, I have no clue why it can't
find a test class directly in it's classpath.
On Tue, Apr 7, 2009 at 7:35 PM, Brett Porter wrote:
> That sounds like a separate problem, howev
That sounds like a separate problem, however I can't tell what is
wrong from the info here. Are you able to check the surefire temporary
files to see if the arguments look reasonable?
- Brett
On 08/04/2009, at 10:27 AM, Tim wrote:
It doesn't show the junit 3 jar but has the same problem:
It doesn't show the junit 3 jar but has the same problem:
Forking command line: /bin/sh -c cd /home/tich/data/bps_trunk/bps-api &&
/usr/lib/jvm/jdk1.6.0_13/jre/bin/java -jar
/tmp/surefirebooter2137625950913122347.jar
/tmp/surefire4278370938049229367tmp /tmp/surefire3389360321643705255tmp
org.apach
Can you try the latest version of the surefire plugin? (v2.4.3)
On 08/04/2009, at 10:15 AM, Tim wrote:
Yea. It's showing up as [INFO]junit:junit:jar:4.4:test with no
version 3
in the list.This is with maven 2.1.0 AND 2.0.10 btw.
The reason that I noticed this was because I have a base tes
Yea. It's showing up as [INFO]junit:junit:jar:4.4:test with no version 3
in the list.This is with maven 2.1.0 AND 2.0.10 btw.
The reason that I noticed this was because I have a base test class in a
dependency that surefire was not able to find. But compilation was fine.
On Tue, Apr 7, 2009 at
have you confirmed that dependency:list only shows junit 4?
On 08/04/2009, at 9:18 AM, Tim wrote:
Why do I see
Forking command line: /usr/lib/jvm/jdk1.6.0_13/jre/bin/java -classpath
/home/tich/.m2/repository/org/apache/maven/surefire/surefire-booter/
2.3/surefire-booter-2.3.jar:/home/tich/.m2
Why do I see
Forking command line: /usr/lib/jvm/jdk1.6.0_13/jre/bin/java -classpath
/home/tich/.m2/repository/org/apache/maven/surefire/surefire-booter/2.3/surefire-booter-2.3.jar:/home/tich/.m2/repository/org/apache/maven/surefire/surefire-api/2.3/surefire-api-2.3.jar:/home/tich/.m2/repository/or
12 matches
Mail list logo
