On Mon, 25 Oct 2004 22:27:55 +0200, "Vincent Massol" <[EMAIL PROTECTED]> wrote:
> With the coming release of Cargo (http://cargo.codehaus.org) I'd like to > start refactoring Cactus to use Cargo. I'll try not to modify the Cactus Ant > API to start with :-) I'm ok with that, but I think we should release a 1.7M1 (Milestone 1) release first. There's been a lot of bug fixes and minor improvement that users cannot take advantage of yet. So, before we starting refactoring, we should: 1.Fix some bugs. I'd like to at least finish: CACTUS-132 (waiting for review) CACTUS-150, CACTUS-129 (need to commit the change to AspectJ 1.2 and change some .aj files) CACTUS-90 (needs test cases and review - we might leave this one for the next release). 2.Release a temporary 1.7 version (like Milestone 1) 3.Start the refactoring, without branching (opcionally, we could create a branch which would later be merged in the main release - this way, we could continue fixing bugs in the main brainch and eventually release a M2 before the Cargo integration is done). > In a second phase, I think the best would be to somehow let Cactus users > directly use the Cargo Ant tasks in order to benefit from all the new > features of Cargo (including the ones to come like hot deployment, etc). In a third phase we should eliminate all the logic on the Ant tasks, so the Maven and Ant modules are independent. I mean, right now the Maven plugin uses the Ant tasks; ideally, the logic should be somewhere else, which would be called by both Maven and Ant. If understood Cactus correctly, it would be the responsible for starting/stopping the containers. We would then need a new module/layer to cactify the war and deploy the war/ear - something like a J2EE module, maybe. > Is that ok with everyone? Yes. -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
