You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by "William Ferguson (JIRA)" <ca...@jakarta.apache.org> on 2006/05/02 03:20:46 UTC
[jira] Updated: (CACTUS-238) Ability for the CactifyEar Task to to
optionally work on an exploded Ear
[ http://issues.apache.org/jira/browse/CACTUS-238?page=all ]
William Ferguson updated CACTUS-238:
------------------------------------
Attachment: cactus-238-patch-all.txt
OK this patch was created from the SVN cdmline so hopefully it can be readily applied.
It contains:
Implementations for the Cargo Archive interfaces for exploded archive formats. I think these should eventually be submitted to Cargo and will look at doing that.
CactifyExplodedEar Ant task.
Modifications to the EarParser such that if Archive is a folder then the cactus task will execute the tests against an exploded Ear.
I also belive I have removed the need for any of the Cargo Archive implementations, that is I think I have switched everything to use Cargo now. So lots of the classes in org.apache.cactus.integration.ant.deployment.*.* can be removed in favour of the Cargo alternatives. Doing so will allow cleanup of the ExplodedArchive versions as all of these needded to explicitly reference the Cargo classes at every point.
> 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-all.txt, 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: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org