Hi Felipe, My current approach is to have 5 steps separately as disscussed with Vincent, so I do not want to break other codes in maven and possible in other places. I will replace the CactusTask with a new one soon, as your suggesion before, the 5 steps may have impact on maven so I will be careful on this.
Also, regarding the cargo tag evaluation, you are right that modifying common-build.xml is not a good way. I attach here a new patch for the one in servlet folder. This keeps the common-build.xml unchanged (not adding anything for cargo). Thanks Xuan -----Original Message----- From: Felipe Leme (JIRA) [mailto:[EMAIL PROTECTED] Sent: Thursday, 21 July 2005 2:03 PM To: cactus-dev@jakarta.apache.org Subject: [jira] Updated: (CACTUS-151) Refactor Ant integration to use Cargo [ http://issues.apache.org/jira/browse/CACTUS-151?page=all ] Felipe Leme updated CACTUS-151: ------------------------------- Attachment: felipeal_after_171_merge.patch Hi Xuan, I applied your patches but haven't ananlyzed the changes yet - although I realized you created a new class called CactusTestTask instead of replacing CactusTaks - is there a reason for that? Also, I'm providing a new patch against the changes I did on the HEAD branch. -- Felipe PS: BTW, please use a 'cvs diff -uN' at the root directory next time you need to submit a patch > Refactor Ant integration to use Cargo > ------------------------------------- > > Key: CACTUS-151 > URL: http://issues.apache.org/jira/browse/CACTUS-151 > Project: Cactus > Type: Task > Components: Ant Integration > Reporter: Vincent Massol > Assignee: Xuan Thang Nguyen > Fix For: 1.8 > Attachments: build.xml, felipeal_after_171_merge.patch, files.zip, > patch20-07.tgz, xnguyen-patch.tgz, xnguyen-patch.tgz > > See http://cargo.codehaus.org -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]