Vincent Massol wrote: [snip]
jakarta-cactus[snip]
|_ anttasks
(only keep in this subproject the Ant tasks that are not related to Cactus. This subproject is expected to disappear over time as
it is expected Ant will provide solutions to perform what we are
doing)
I'll take this as an opportunity to assemble an overview of what currently exists in the anttasks module, and attach my thoughts about each of the parts ...
---- Used at build time ----
----------------------------------------------------------
org.apache.cactus.ant.ArgListTask
----------------------------------------------------------
I haven't completely understood why this task exists. IMHO
it could be just kicked out (deprecated ;-) ), and its use
replaced with the normal <arg>, <vmarg> and <sysproperty>
stuff instead, which also have more power when it comes to
handling paths etc.
----------------------------------------------------------
org.apache.cactus.ant.ChangeLogTask
----------------------------------------------------------
Without having looked at it closely, couldn't the use of
this task be replaced with the standard <cvschangelog> ?
----------------------------------------------------------
org.apache.cactus.ant.CheckPropertiesTask
org.apache.cactus.ant.CheckPropertyItem
org.apache.cactus.ant.PropertyName
----------------------------------------------------------
All for checking whether a specific property has been set,
and optionally if it refers to an existing file. It is
used to check whether required JAR locations have been set
as properties, bailing if not. In addition, it outputs the
value of the properties.
IMHO, this task can be replaced by standard mechanisms,
using <available>, <fail>, etc. The drawback is a somewhat
longer build file.
I'd like to avoid having to compile Ant tasks before being able to compile the framework. I think that for <argList> and <checkProperties> the additional overhead is not warranted. But just IMHO ;-)
---- Used at run time ----
------------------------------------------------------------
org.apache.cactus.ant.AbstractServerRun
org.apache.cactus.ant.EnhydraRun
org.apache.cactus.ant.ResinRun
------------------------------------------------------------
These are all classes for starting/stopping containers.
IMHO they could be useful outside of the Ant tasks module.
What about moving them into the framework?
------------------------------------------------------------
org.apache.cactus.ant.RunServerTestsTask
org.apache.cactus.ant.StartServerHelper
org.apache.cactus.ant.StartServerTask
org.apache.cactus.ant.StopServerHelper
org.apache.cactus.ant.StopServerTask
------------------------------------------------------------
The <runservertests>-Task is probably the only task from
this module that most (all?) users have ever used. I'm not
sure about use cases for the StartServerTask/StopServerTask.
But overall, this code should stay where it is (speaking of
packages), but moved to frontends/ant eventually.
We should have an example that uses <parallel>/<sequential>/<http>/<waitfor> instead of
<runservertests>.
--
Christopher Lenz
/=/ cmlenz at gmx.de
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
