[ http://issues.apache.org/jira/browse/CACTUS-238?page=all ]
William Ferguson updated CACTUS-238:
------------------------------------
Attachment: cactus-238-patch-from-svn-cmdline.txt
This patch was created from the SVN cmdline after updating to revision 394831.
The previous patch was created from within Eclipse and appears to contain fully
qualified paths instead of relative ones, which may be why Fellipe could not
apply it.
> 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-from-svn-cmdline.txt, 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]
