On 3/19/06, William Ferguson <[EMAIL PROTECTED]> wrote: > 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? > <snip/>
Hi William- Since cactus (as the whole of jakarta) now uses SVN, the correct URL is: http://svn.apache.org/repos/asf/jakarta/cactus/trunk/ Other related information about creating patches, the process for submissions etc. is here: http://jakarta.apache.org/site/getinvolved.html I have opened a documentation issue [1] to increase the probability that the website will be updated with the corrections. -Rahul [1] https://issues.apache.org/jira/browse/CACTUS-239 > William > > > -----Original Message----- > From: William Ferguson (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Monday, 20 March 2006 10:31 AM > To: [email protected] > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
