Change Cactus:single Target?

[EP...@upstate.com]

Hi all,

I am looking at the cactus:single target..  And it seems to me a pain to
have to deploy the war ahead of time.  I would like to make cactus:single
work the same as cactus:test-tomcat-4x, but only for a specific testcase.

What do you think of tweaking the signature to be cactus:single
-Dtarget=myTest -Dplatform=tomcat-4x 

Attached is a patch file for the cactus plugin.jelly.

Eric Pugh

RE: Change Cactus:single Target?

[Vincent Massol <vm...@octo.com>]

 

 

-----Original Message-----
From: EPugh@upstate.com [mailto:EPugh@upstate.com] 
Sent: 18 December 2002 17:47
To: turbine-maven-dev@jakarta.apache.org
Subject: <PATCH> Change Cactus:single Target?

 

Hi all, 

I am looking at the cactus:single target..  And it seems to me a pain to
have to deploy the war ahead of time.  I would like to make
cactus:single work the same as cactus:test-tomcat-4x, but only for a
specific testcase.

cool

What do you think of tweaking the signature to be cactus:single
-Dtarget=myTest -Dplatform=tomcat-4x 

I like it. However, I'd like to propose a minor naming modification. All
the cactus plugin properties are prefixed with maven.cactus. Thus could
we name the properties:

maven.cactus.singletest  and maven.cactus.container

The rationale is that you could have the maven.cactus.platform property
defined in your build.properties (to avoid typing it all the time - it
is actually quite seldom you have to switch containers, right?). Thus
you could avoid typing the -Dmaven.cactus.container=xxxx

In addition we could add a "cactus:test" goal that would do exactly the
same as "cactus:test-tomcat-4x" but use the maven.cactus.container to
find on which container to run the tests.

The problem with the "target" property is that if another plugin is
using the "target" property, it will clash with it (I think).

What do you think?

Attached is a patch file for the cactus plugin.jelly. 

Eric Pugh 

  Thanks

-Vincent