I noticed this thread from a while back but there was never a
resolution.  We are trying to get our parasoft jtest generated test
cases to run under Maven 2 and the surefire plugin with not much
success.  It looks like parasoft itself it spinning up its own
classloader with the incorrect classpath.  Has anyone had any luck
getting jtest unit cases to run under Maven 2 and the surefire plugin?


Scott Ryan


When I moved the dependencies to be only under the durefire plugin, the
[compiler:testCompile]
goal failed with compile errors, so I left them both at the top level of
the POM, and added
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
 
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" <[email protected]>; "Maven Users List" 
<[email protected]>
Sent: Thursday, June 08, 2006 3:09 PM
Subject: RE: Using 3rd party jar with surefire



  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>


- - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the 
designated recipient(s) named. If you are not the intended recipient of this 
message, you are hereby notified that any review, dissemination, distribution 
or copying of this message is strictly prohibited. This communication is for 
information purposes only and should not be regarded as an offer to sell or as 
a solicitation of an offer to buy any financial product, an official 
confirmation of any transaction, or as an official statement of Aurora Loan 
Services. Email transmission cannot be guaranteed to be secure or error-free. 
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such. All information is subject to change 
without notice.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to