Unico Hommes wrote:
Nice article!
We do basically the same thing. Note that with MountTableMatcher you no longer need to patch the cocoon root sitemap.
Why people often say so? There is no need to patch the root sitemap anyway as it is simply trying to mount whatever comes in as request URL on to the filesystem. Just deploy you app as a subdirectory of the webadd directory of Cocoon. Sure, if you need to have your start URL to be the root just copy a different welcome.xml/welcome.xslt over.
It is too bad that Ant does not itself support a pluggable architecture.
Now you end up replicating such a build environment in every new
project.
Use another one instead (Maven, Centipede) that has 'plugins'.
If something changes in cocoon that impacts the build system you need to update all those separate instances. I started on a Maven plugin for cocoon some time ago exactly for this reason. But unfortunately haven't been able to work on it lately. Maybe something for CTP if that would prove to take off.
We already have such Maven plugins and if CTP will start we sure will contribute.
Regards, Unico
-----Original Message-----
From: Jeremy Quinn [mailto:[EMAIL PROTECTED] Sent: woensdag 19 november 2003 16:41
To: [EMAIL PROTECTED]
On 17 Nov 2003, at 23:03, Geoff Howard wrote:
Interesting. I'd rather integrate my build into Cocoon's,
rather than
the other way around, and now I can see that all I've got to do is stick files into a confpatch folder, which is really great.
Sure, but some people prefer to integrate Cocoon into their build - and generally want to do so with as little "building" of Cocoon as possible. Either way works well.
With this recent change to XConfPatchTask, I have been able to refactor the way we build our Projects 'into' Cocoon.
I attempt to describe the process here:We've never ha
http://wiki.cocoondev.org/Wiki.jsp?page=ProjectBuilding
HTH
regards Jeremy
-- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
