Hi Geoff. Please change it. I just follow the Niclas' advise. ;-)
Are there some mock classes to address that? Best Regards, Antonio Gallardo Geoff Howard dijo: > And whole of cocoon was not at stake, just the eventcache block. > There is one (?)class in eventcache which provides support for JMS > messages invalidating cache (which in my original vision was the > primary use) and thus this dependency on the JMS api. Do we in gump, > or in blocks build have "conditional"/optional dependencies? IOW, > this block can actually function usefully without JMS except I believe > this one impl class. > > Geoff > > > On Wed, 17 Nov 2004 07:21:00 -0600 (CST), Antonio Gallardo > <[EMAIL PROTECTED]> wrote: >> Upayavira dijo: >> >> >> > [EMAIL PROTECTED] wrote: >> > >> >>Author: antonio >> >>Date: Wed Nov 17 05:11:21 2004 >> >>New Revision: 76124 >> >> >> >>Modified: >> >> cocoon/trunk/gump.xml >> >>Log: >> >>Fix eventcache. Thanks to Niclas Hedhman. >> >> >> >>Modified: cocoon/trunk/gump.xml >> >>============================================================================== >> >>--- cocoon/trunk/gump.xml (original) >> >>+++ cocoon/trunk/gump.xml Wed Nov 17 05:11:21 2004 >> >>@@ -905,6 +905,7 @@ >> >> >> >> <depend project="cocoon" inherit="all"/> >> >> <depend project="cocoon-block-jms"/> >> >>+ <depend project="jms"/> >> >> <depend project="cocoon-block-xsp" type="samples"/> >> >> >> >> <work nested="build/cocoon-@@DATE@@/blocks/eventcache/dest"/> >> >> >> >> >> > Is this right? Surely it is the cocoon-block-jms 'project' that is >> > dependent upon JMS, not the whole of Cocoon? >> >> The cocoon-block-jms project already had this dependency too. >> >> Best Regards, >> >> Antonio Gallardo >> >> >
