Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <E37F8F79E39C0943A8E2846F1C4EA9F2082A12BF@mail003.unimaas.nl>
From: H.vanderLinden@MI.unimaas.nl
To: dev@cocoon.apache.org
Subject: RE: Cocoon + "private" project + CVS use, best practice?
Date: Mon, 2 Feb 2004 15:37:59 +0100 
MIME-Version: 1.0
Content-Type: text/plain

Hi guys,

thank you all for the suggestions. Reading your answers I realised I didn't
present my question clearly enough. I wanted to know a way of building my
own CVS that includes both "standard cocoon" and my own project, but I
suppose I should think in another way.
What I needed most was probably the Wiki page (I had come across this once,
but couldn't find it any more, so thanks for the link). 
What I do now is modify the files in a running Tomcat webapp to quickly
test/develop. I really like this due to the speed of development. Following
the setup of the Wiki page, I will loose this speed. I'll think this over,
but if anyone has comments please provide them.

Bye, Helma

> -----Original Message-----
> From: Upayavira [mailto:uv@upaya.co.uk] 
> Sent: Tuesday, 27 January 2004 15:34
> To: dev@cocoon.apache.org
> Subject: Re: Cocoon + "private" project + CVS use, best practice?
> 
> 
> Geoff Howard wrote:
> 
> > H.vanderLinden@MI.unimaas.nl wrote:
> >
> >> Hi,
> >>
> >> I would like to know how others have setup their systems to use 
> >> Cocoon from
> >> the CVS and backup their own project into another CVS.
> >> Currently I update a local CVS repository from the Cocoon 
> CVS, build it,
> >> copy all new files/jars etc. to another tree where I build my own 
> >> project.
> >> I have a feeling this could be much more efficient.
> >
> >
> > Another option would be to skip the copy step, keep your 
> application 
> > in its separate tree, and use the xpatch task in cocoon's build to 
> > perform the necessary customizations (changes to cocoon.xconf, 
> > web.xml, root sitemap, etc.).  The root sitemap should be able to 
> > mount a sub-sitemap outside of the context root.  You can even keep 
> > your xpatch files in your dev tree - the directory used is 
> > configurable via ant parameter. Your built app would then be in 
> > Cocoon's cvs tree unless you change Cocoon's target config 
> to your own 
> > dev tree.  The downside is that you cannot store the 
> version of Cocoon 
> > you are built on in your cvs tree.  I would highly 
> reccomend keeping 
> > the cvs update timestamp stored somewhere in your cvs so 
> you can roll 
> > back to a last known working version if something should break.
> 
> Further to this, what I've done on a project is add a target to my 
> projects Ant script to copy patch files from my directory tree into 
> Cocoon's. It even then runs Cocoon's build script itself. So, 
> you type 
> ant build-webapp, it untars the Cocoon archive, copies across 
> all of the 
> customising libs and patch files, and local.blocks/build.properties, 
> calls Cocoon's build process, and then copies the built 
> webapp into its 
> final resting place. That way, to deploy the app onto another 
> machine, 
> or to upgrade the Cocoon webapp is as simple as 'ant 
> build-webapp', even 
> if the Cocoon needs lots of customisation. Works a treat.
> 
> Regards, Upayavira
> 
>