Hi Per,
You should really use the Ant-based build for now. This is the current official build and is documented on Cactus web site. The Maven build is a work in progress, it is far from being finished and is not documented yet. That's unless you're a Maven expert and wish to help us improve the Maven build :-)
Thanks -Vincent
In the context of our build system, I'd like to eventually experiment with Ant 1.6, which I think could considerably simplify our build too. The new tasks such as <subant>, <macrodef> and <presetdef> and <import> look pretty damn cool [1]. And as we're targetting a non-released version of Maven, it's only fair to compare against the latest and greatest of Ant ;-)
I'm not yet convinced about switching to Maven. Looking at the xdoc plugin, I'm rather opposed to the approach used (JSL and a bunch of color properties) and I find it really hard to believe that the main communication channel between the report generators and the documentation generation -- the XML document format -- is not even based on a formal schema. The need to provide a jelly script just to enable multiple parallel source paths for compilation is just silly -- the POM is obviously too limited here, and it gets worked around with scripting. :-(
-chris
[1] http://nagoya.apache.org/wiki/apachewiki.cgi?NewAntFeaturesInDetail
-- Christopher Lenz /=/ cmlenz at gmx.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
