Cocoon and JCS (on Gump)

Dear JCS folks,

Could somebody look into this please, and provide the Cocoon community
with some guidance? Is this a permenant change? Is this something that will 
cause a disconnect in the field (in environments where old jars mix with new?)

regards

Adam
----- Original Message ----- 
From: "Adam R. B. Jack" <ajack@xxxxxxxxxxxxx>
To: "Turbine JCS Developers List" <turbine-jcs-dev@xxxxxxxxxxxxxxxxxx>
Sent: Thursday, July 29, 2004 8:19 PM
Subject: Fw: [GUMP][PATCH] cocoon seems to require log4j


> Can you folks look at this, for the Cocoon community? Did this change (it
> appears so) and if so, did it need to? What can we do to smooth a transition
> in the field (in environments running on different releases).
>
> regards
>
> Adam
> > Although it seems there may still be something to fix:
> >
> >
> http://brutus.apache.org/gump/public/cocoon-2.1/cocoon/gump_work/build_cocoon-2.1_cocoon.html
> >
> >
> http://brutus.apache.org/gump/public/cocoon-2.1/cocoon/gump_work/build_cocoon-2.1_cocoon.txt
> >
> >   [javac]
> >
> /usr/local/gump/public/workspace/cocoon-2.1/src/java/org/apache/cocoon/compo
> > nents/store/impl/JCSDefaultStore.java:361: dispose() in
> > org.apache.cocoon.components.store.impl.JCSDefaultStore.JCSCacheAccess
> > cannot override dispose() in org.apache.jcs.access.CacheAccess; attempting
> > to assign weaker access privileges; was public
> >     [javac]         protected void dispose() {
> >     [javac]                        ^
> >     [javac] 1 error
--
Have you Gump'ed your code today?
http://gump.apache.org