On 19 Nov 2003, at 16:19, Unico Hommes wrote:
Nice article!
Thanks Unico !
We do basically the same thing. Note that with MountTableMatcher you no longer need to patch the cocoon root sitemap.
It was a toss-up between patching the root sitemap, or patching the mount-table.xml ;)
Basically I still needed the same dynamic parameters from the users environment ....
It is too bad that Ant does not itself support a pluggable architecture.
Too true
Now you end up replicating such a build environment in every new project. If something changes in cocoon that impacts the build system you need to update all those separate instances.
exactly
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.
interesting ... I have done very little with Maven ...
regards Jeremy
-----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:
rather than
Interesting. I'd rather integrate my build into Cocoon's,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:
http://wiki.cocoondev.org/Wiki.jsp?page=ProjectBuilding
HTH
regards Jeremy
smime.p7s
Description: S/MIME cryptographic signature
