RE: [jira] Created: (CACTUS-238) Ability for the CactifyEar Task to to optionally work on an exploded Ear

[William Ferguson <Wi...@contractorsolutions.com.au>]

OK,

I have created a version of the cactifyear task (CactifyExplodedEar)
that cactifies a folder that contains Ear content. This class is
attached to the issue. I have also included the patch to the build xml
to ensure that the task is included in the cactus.tasks resource.

The Task only needs a single srcfile attribute which defines the folder
to 
cactify. Ie the target folder is modified, a new folder is not created.

It may also contain a cactuswar element as per cactifyear.

It does not added EJB refs to the embedded Cactus WAR.

I'll work out some interim solution for our in house projects, but is it
possible to get this task incorporated into future versions of Cactus?
If some other artefacts need to be created, let me know and I'll throw
some time at it.

William


-----Original Message-----
From: William Ferguson
[mailto:William.Ferguson@contractorsolutions.com.au] 
Sent: Monday, 20 March 2006 10:44 AM
To: Cactus Developers List
Subject: RE: [jira] Created: (CACTUS-238) Ability for the CactifyEar
Task to to optionally work on an exploded Ear

Hi all,

I really need this functionality in order to get my team onto the path
of regular (in container) testing. 

I'm more than happy to cut the code myself and supply it as patch if you
think it's a worthwhile contribution, otherwise I'll make the
modifications to a local copy of Cactus and we'll just use it in house.

But I'm having trouble checking out the code from CVS.
The link to CVS (http://cvs.apache.org/viewcvs/jakarta-cactus/) at
http://jakarta.apache.org/cactus/participating/index.html seems to be
broken as it returns a 404 Not Found and provides Python Traceback.
Can someone point me in the right direction?

William


-----Original Message-----
From: William Ferguson (JIRA) [mailto:cactus-dev@jakarta.apache.org] 
Sent: Monday, 20 March 2006 10:31 AM
To: cactus-dev@jakarta.apache.org
Subject: [jira] Created: (CACTUS-238) Ability for the CactifyEar Task to
to optionally work on an exploded Ear

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


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


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org