If I understand you correctly you want to bind the cargo plugin to the
pre-integration phase. I common scenario.
I did a quick search and found this example:
http://www.jitr.org/useCaseStudy.html
/Anders
On Fri, Jan 15, 2010 at 11:05, fabrice.mercier1 beufm...@yahoo.fr wrote:
Hi
I have a
' Subject: RE: Maven and Integration Test
-Original Message- From: Amato Massimiliano (TLAB)
[mailto:[EMAIL PROTECTED] Sent:
Wednesday, May 19, 2004 4:17 PM To: Maven Users List Subject:
Maven and Integration Test
Hello,
I've a problem with my integration tests
[mailto:[EMAIL PROTECTED]
Sent: 20 May 2004 20:10
To: Maven Users List
Subject: Re: Maven and Integration Test
The most elagent solution I've seen to date is simply another project
as Michal has suggested. By the OP's definition, these tests span
multiple aritfacts/projects and require
-Original Message-
From: Amato Massimiliano (TLAB)
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 4:17 PM
To: Maven Users List
Subject: Maven and Integration Test
Hello,
I've a problem with my integration tests.
In my system we have both unit and integration
Hi,
+) I have a couple of projects to build and run the JUNIT tests and in my EAR project
I automatically deploy to BEA WebLogic to run my webtest.
+) I currently reintegrate CLOVER to get the test coverage for the web regression tests
Cheers,
Siegfried Goeschl
-Original Message-
-Original Message-
From: Ryan Sonnek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 4:46 PM
To: Maven Users List
Subject: RE: Maven and Integration Test
I was REALLY hoping to hear another solution to this problem.
I'm running into the same thing, and would like
