Gregor J. Rothfuss wrote:
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?
I am not talking about downloading stuff automatically, but to validate
the dependencies and requirements, which is not exactly the
same thing, whereas introducing Maven does certainly make sense. But I
am talking something similar to Gump.
I don't think Lenya 1.4 is very far away, whereas I cannot say that for
Cocoon 2.2, so I don't think it's a good
idea to base Lenya 1.4 on Cocoon 2.2
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
