, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven-2.0.6 throws NPE in surefire
It is version 2.3 and the same version was used in both maven-2.0.5 and
maven-2.0.6. However, only maven-2.0.6 produces the NPE. Seems like
there was bug introduced in maven-2.0.6.
Also, I had a clean repo for
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 01, 2007 1:06 PM
To: Maven Users List
Subject: maven-2.0.6 throws NPE in surefire
This works fine in maven-2.0.5.
I have the following surefire configuration
Thanks! But I worked around it by removing the system properties that
I was trying to define (the unit test case now defines them.)
Regards,
Hiram
On 3/14/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> 2006/3/13, Hiram Chirino <[EMAIL PROTECTED]>:
>
> > I was just using the latest deployed 2.1
2006/3/13, Hiram Chirino <[EMAIL PROTECTED]>:
> I was just using the latest deployed 2.1.3-SNAPSHOT version of
> surefire and I got this error on the activemq/activemq-jaas module.
> Any idea?
...
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:396)
> a
i don't see this problem
On 3/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Hi Everybody,
>
> I was just using the latest deployed 2.1.3-SNAPSHOT version of
> surefire and I got this error on the activemq/activemq-jaas module.
> Any idea?
>
>
> [WARNING] POM for 'directory-asn1:asn1-der:pom:0.
Hi Everybody,
I was just using the latest deployed 2.1.3-SNAPSHOT version of
surefire and I got this error on the activemq/activemq-jaas module.
Any idea?
[WARNING] POM for 'directory-asn1:asn1-der:pom:0.3.2' is invalid. It
will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WAR
