Hi Felipe, That patch was created using Eclipse and I now notice that it contains fully qualified paths instead of relative ones. I have submitted a new patch created via the SVN cmd line. It is also based upon revision 394831 which is more recent. See how you go with that.
I'll start working on a test case and some doco. William -----Original Message----- From: Felipe Leme (JIRA) [mailto:[EMAIL PROTECTED] Sent: Sunday, 16 April 2006 10:30 AM To: [email protected] Subject: [jira] Commented: (CACTUS-238) Ability for the CactifyEar Task to to optionally work on an exploded Ear [ http://issues.apache.org/jira/browse/CACTUS-238?page=comments#action_123 74662 ] Felipe Leme commented on CACTUS-238: ------------------------------------ Hi William, I've tried to apply your patch, but it failed: [EMAIL PROTECTED]/Users/felipeal/cvs/cactus/trunk: patch -p0 < /Users/felipeal/cvs/patches/CACTUS-238/cactus-238-patch.txt (Stripping trailing CRs from patch.) patching file D:/Modules/cactus-cvs/integration/ant/src/java/org/apache/cactus/integra tion/ant/deployment/application/ExplodedEarArchive.java (Stripping trailing CRs from patch.) patching file D:/Modules/cactus-cvs/integration/ant/src/java/org/apache/cactus/integra tion/ant/deployment/ExplodedJarArchive.java (Stripping trailing CRs from patch.) can't find file to patch at input line 247 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: D:/Modules/cactus-cvs/integration/ant/src/java/org/apache/cactus/integra tion/ant/deployment/EarParser.java |=================================================================== |--- D:/Modules/cactus-cvs/integration/ant/src/java/org/apache/cactus/integra tion/ant/deployment/EarParser.java (revision 387121) |+++ D:/Modules/cactus-cvs/integration/ant/src/java/org/apache/cactus/integra tion/ant/deployment/EarParser.java (working copy) -------------------------- Could you please provide a new patch against SVN's trunk? Also, a test case for the new feature would be welcome. Regarding the documentation, it's on documentation/docs/xdocs; you go to the documentation dir, run 'ant dist' and the documentation will be available on documentation/target/doc/index.html . I think you will need to add a new xml describing the task on documentation/docs/xdocs/integration/ant (you can use the existing xmls as template) and also an entry in the sitemap.xml -- Felipe > Ability for the CactifyEar Task to to optionally work on an exploded Ear > ------------------------------------------------------------------------ > > Key: CACTUS-238 > URL: http://issues.apache.org/jira/browse/CACTUS-238 > Project: Cactus > Type: Improvement > Components: Ant Integration > Versions: 1.7.1 > Reporter: William Ferguson > Attachments: CactifyExplodedEarTask.java, cactus-238-patch.txt, patch-to-build-xml.txt > > We're using Weblogic 8.1 and in development we deploy the application as an exploded Ear to allow hot deployment of JSPs and a quick turn around. > Because the developers are used to such quick turn arounds time it makes it very hard to convince them to build a full Eay, cactify it and then delpoy as it adds an extra couple of minutes to each build cycle. Which means that they ignore the UnitTests. > It would be really useful if the CactifyEar task could be configured so that it could cactify an exploded appllication. > I think this will just involved > 1) creating the Cactus war in the appropriate place > 2) adding a module for the cactus war in the application xml of the exploded Ear -- 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]
