Vincent Massol wrote:
The goal of this Cargo refactoring is really to remove all aspects of
container configuration and manipulation from Cactus. Thus it should be
possible for someone to use his/her own ways of doing this or to use Cargo
which should integrate well.
I agree. In particular, sometimes you need to run the test in a
container that is already running (and shouldn't be started again by
Cacctus).
That said, I don't see much advantage of having that and I think I would
prefer the 5 steps above.
What do other think?
I'm not sure if I understood it, but if I did, you mean there are too
possible ways to use Cactus integrated with Cargo (on Ant):
1.User must define all (5) steps on build.xml
2.We supply a <cactus> tag that does everything.
I particularly think we should offer both options, i.e., a single task
that does everything based on properties and another task that lets the
user define what to do.
Also, note that #2 is the way that Maven works, so if we move that
funcionality to a proper Ant task, the maven plugin would be much simpler.
-- Felipe
PS: I will try to fix the last bugs before the 1.7.1 release tonight and
then create the CVS branch for it...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
