Hi all,
As I mentioned earlier in the list, the main area where we need help
is the Cargo integration stuff, so I will try to explain how one can
help us in that area.
First, the current status: I've had applied Xuan's last patches and
also upgraded the Cargo dependency to 0.8, which broke some stuff,
both in the Java API (for instance, the AntMonitor class was replaced
by AntLogger) and Ant tasks (there is no more <war> or <ear> tasks but
a generic <deployable> instead). I fixed those breaks at the point
where Cactus compile and the Ant tasks are run, but I'm afraid I
didn't fixed it all, as I cannot run the samples - they all stuck when
running the tests:
test-container-internal-ok:
[echo] Running tests on resin3x container...
[mkdir] Created dir:
/Users/felipeal/cvs/cactus/trunk/samples/servlet/target-13/test/resin3x
[mkdir] Created dir:
/Users/felipeal/cvs/cactus/trunk/samples/servlet/target-13/test/resin3x/config
[cargo] DEPRECATION WARNING: Please use the configuration home
element instead of the configuration dir element which is now
deprecated
Overriding previous definition of reference to resin3x
(I've tried with tomcat5x, jboss4x and jboss3x and the results are the same).
So, here's how you can help:
- download the latest Cactus from SVN (svn co
https://svn.apache.org/repos/asf/jakarta/cactus/trunk/)
- build cactus withough setting any container on
$HOME/build.properties (ant dist)
- now add one (or more) container's property on $HOME/build.properties
(for instance, cactus.home.jboss4x=/usr/local/java/jboss-4.0.3RC2), go
to the samples/ejb or samples/servlet and run 'ant dist'
- if the tests didn't work, try to figure it out why (and fix it :-);
if necessary to send a patch, use CACTUS-151
(http://issues.apache.org/jira/browse/CACTUS-151)
- once the tests are working, you can try to run a 'ant clean release'
from the root directory (and with the containers properties set)
Other areas of help are:
- how to run the tests without setting the properties, i.e, using
Cargo's zip-installer features
- test the maven plugin (which was also updated to Cargo 0.8)
The 'figure it out why' step may sound a little bit harsh, but
unfortunately that's where we (at least I - I'm not as familiar with
Cargo as Vincent and others) are stuck at the moment.
[],
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
