cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <>
Subject Re: [WARNING] Incompatible change (was Re: DELI support added)
Date Thu, 10 Jan 2002 22:54:16 GMT
I guess the problem comes from the fact that cocoon.jar was built with
the Deli classes in it. I'll update the build.xml to verify the
presence of Deli libraries, and skip the compilation if they are not


On Thu, 10 Jan 2002 16:36:27 -0500, Berin Loritsch <> wrote:

> Davanum Srinivas wrote:
> > Mark,
> > 
> > :) Once you jumpstart us...We can maintain this in Cocoon CVS Repository.
> Great work with incorporating DELI, however any webapp that doesn't use or
> "need" it's support won't run if the jar is not available--even if I don't
> refer to it in the sitemap or cocoon.xconf.
> This is considered a backwards incompatible change.  We need to strive to
> make Cocoon work even if a jar is absent.  I will temporarily add the DELI
> jar to my webapp, but I should not be forced to do so if I am not using
> the Component.
> Any time you add a new Component that requires another third party jar to
> Cocoon, PLEASE TEST WITHOUT THE JAR.  Make sure your new Component does not
> place any artificial constraints on other developers.  This will help make
> a lean and mean Cocoon.
> More importantly, we should strive to make Cocoon work even if there are
> no third-party jars in the system.  BTW, this does not apply to the Avalon
> jars since Cocoon was built with the architecture.
> -- 
> "They that give up essential liberty to obtain a little temporary safety
>   deserve neither liberty nor safety."
>                  - Benjamin Franklin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message