Hi,
This is some brainstorming ideas about the new "ant" subproject which
would provide reusable Ant scriptlets for persons wishing to use Ant as
their front end to run Cactus tests. The idea is the same than Maven,
i.e. to provide reusable best practices, directly usable by project Ant
scripts.
The only real question is packaging. I would suggest this subproject
should deliver a single jar file containing:
- Ant tasks (the existing ones): RunServerTestsTask, StartServerTask,
etc
- Ant scripts for different containers
- A special Ant task that would be the equivalent of the Ant <ant> task
BUT that would allow to execute build files located inside a jar.
Here are some potential usage scenarios:
<target name="test">
<property name="cactus.framework.jar" value="${lib.dir}/cactus.jar"/>
<property name="cactus.junit.jar" value="${lib.dir}/junit.jar"/>
<property name="cactus.httpclient.jar"
value="${lib.dir}/httpclient.jar"/>
<property name="cactus.commons-logging.jar"
value="${lib.dir}/commons-logging.jar"/>
[...]
<cactusCall buildfile="tomcat.4x.xml" jar="cactus-ant.jar"
target="test">
<param name="cactus.home" value="c:/apps/tomcat-4.1.18"/>
<param name="cactus.port" value="8080"/>
<param name="cactus.workdir" value="${target.dir}/tomcat"/>
<param name="cactus.war" value="${target.dir}/myapp.war"/>
</cactusCall>
</target>
Note1: The <params> can also be set as normal Ant properties.
Note2: The "test" target is the one that does it all, including
cactifying the application war by adding the cactus jars, etc.
Of course, we need to precisely define:
- the full list of properties that our Ant scriptlets will need
- the full list of targets provided by our Ant scriptlets
- the behaviours we want
Note: The only pity is that users still need to care about the cactus
jars. That's the advantage of Maven with its remote/local repositories.
So, what do you think?
Thanks
-Vincent
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
