Yes, but I also add the parasoft jtest and junit jars, and the junit-addons,
as below;
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>parasoft.com</groupId>
<artifactId>jtest</artifactId>
<version>7.5.43</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>parasoft.com</groupId>
<artifactId>junit</artifactId>
<version>7.5.43</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit-addons</groupId>
<artifactId>junit-addons</artifactId>
<version>1.4</version>
<scope>test</scope>
</dependency>
</dependencies>
-----Original Message-----
From: Thorsten Heit [mailto:[EMAIL PROTECTED]
Sent: Thu 6/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", 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 below. Is there a reason this should not work, or is
> there something I can do to make it work?
Do you have JUnit in your class path? In my pom.xml I have the following
dependency for the unit tests:
<dependencies>
...
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
...
</dependencies>
HTH
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
iD8DBQFEiC1FQvObkgCcDe0RAsGaAKCziQzCqBu6IWvnyz3jqEwvKVQP/gCgvdiy
rOmoQwzVLHzGECjvhqTHzjs=
=VFe2
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
