> -----Original Message----- > From: Felipe Leme [mailto:[EMAIL PROTECTED] > Sent: mardi 12 juillet 2005 01:40 > To: Cactus Developers List > Subject: Re: Cactus & Cargo Integration > > 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.
Why not. However, I'd be in favor of implementing approach 1 first and do 2 later on. > 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. Ant is about providing small tasks to users so that he/she can integrate them in his/her own build. They are small building blocks. Maven's approach is completely different. It does not provide building block: it provides full-fledged build features. In any case, I don't disagree! :-) I just think it's more important to provide 1 first and I'm just wondering whether we have the time/energy to maintain the 2 approaches. But if there are Cactus committers willing to support the 2 approaches, I think it's fine! [snip] Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
