Ive now trying a different strategy. I have an integration module which
has the test classes and does the cactus/cargo thing but refers to the
war build in the web project.
On Fri, 2008-09-26 at 13:44 +0200, [EMAIL PROTECTED] wrote:
> as far as I can see, you have to treat test and production vers
24/09/2008 15:30
cc
Por favor, Asunto
responda a
cc
Por favor, Asunto
responda a Re: samples servlet test classes
"Cactus Users
Thanks
On Wed, 2008-09-24 at 16:30 +0300, Petar Tahchiev wrote:
> If you want to try it, please update the integration/maven2 module and
> the samples/servlet module and recompile.
>
--
regards
Martin West
07879 680096
skype:amartinwest
---
Hi Martni,
I just changed the Maven mojo to add the cactus test classes
to the cactified war. This way you can place your tests in
src/test/java
and Maven will compile them in target/test-classes/
And then you can call the mojo like that:
target/test-classes
The better way to address this problem is add the test classes to the
cactified war as part of the cactify task. Otherwise you have to have
special processing to build test and producton versions of the
applicaton war.
On Mon, 2008-09-22 at 21:53 +0100, Martin West wrote:
> Another observation, al