them as dependencies to the surefire plugin. I figure that can't hurt.
Alas, the result
is the same as before.
-Original Message-
From: Kieran Brady [mailto:[EMAIL PROTECTED]
Sent: Thu 6/8/2006 10:19 AM
To: Maven Users List
Subject: Re: Using 3rd party jar with surefire
Someth
same as before.
-Original Message-
From: Kieran Brady [mailto:[EMAIL PROTECTED]
Sent: Thu 6/8/2006 10:19 AM
To: Maven Users List
Subject: Re: Using 3rd party jar with surefire
Something I would try would be adding those as dependencies to the surefire
plugin.
HTH
- Original Me
Something I would try would be adding those as dependencies to the surefire
plugin.
HTH
- Original Message -
From: "Brown, Charles" <[EMAIL PROTECTED]>
To: "Maven Users List" ; "Maven Users List"
Sent: Thursday, June 08, 2006 3:09 PM
Subject: R
/8/2006 9:59 AM
To: Maven Users List
Subject: Re: Using 3rd party jar with surefire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Charles,
> We use Parasoft JTest to generate JUnit based unit tests. Afterward,
> I am able to run them in eclipse using "Run As -> JUnit Test&quo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Charles,
> We use Parasoft JTest to generate JUnit based unit tests. Afterward,
> I am able to run them in eclipse using "Run As -> JUnit Test", and
> they work fine. So, I think I should be able to run them using
> surefire, as long as I have th
All,
We use Parasoft JTest to generate JUnit based unit tests. Afterward, I am
able to run them in eclipse using "Run As -> JUnit Test", and they work fine.
So, I think I should be able to run them using surefire, as long as I have the
parasoft jars on the classpath, but I get the errors
