Andreas Hartmann wrote:
Michael Wechner wrote:
[EMAIL PROTECTED] wrote:
On 2/22/06, Michael Wechner <[EMAIL PROTECTED]> wrote:
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.
Or if a publication is based on Cocoon 2.1.8, but the build is being
done on Cocoon-2.1.9-dev then also an error should be thrown.
This way we are able to reduce questions and time consuming debugging
for something actual obvious.
WDYT?
I think this is a more ambitious version of:
"Check Xalan libraries during install/boot"
http://issues.apache.org/bugzilla/show_bug.cgi?id=35305
and I am all for it.
we can start it simple by it least checking if the modules have been
included by name.
Before building our own dependency resolving mechanism, I'd rather
review the Cocoon block concept again (maybe they allow external
blocks by now) and convert modules to blocks if this is appropriate.
sure, but as said it's not about building something very complex, but
very simple.
It's basically parsing publication.xconf and check if the modules listed
there are
actually available ...
Michi
-- Andreas
--
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]
