Michael Wechner wrote:
Hi
I think we should extend the build process (but also hot pluggable
in a second phase) that requirements and dependencies of each
publication are being checked.
E.g. if a publication is dependent on the module "atom-entry" and
this module has not been referenced, then an error should be thrown.
it might be possible to use the mavenized cocoon 2.2 for this. i tried
to run lenya under cocoon 2.2 about a year ago, it worked reasonably
well. given that 1.4 is still a fair bit away, why not base it on 2.2?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
