Leo Simons wrote: ...
avalon-framework very rarely doesn't get built by gump. It's the ECM dependency that's causing the ripples, and the big set of dependencies ECM has itself.
Since it seems ECM is being put into the freezer anyway, just be pragmatic and make the gump build of cocoon depend on an installed package or some jars in cvs. It's not like ECM has changed a lot over the last 2 years.
Good suggestion as an interim solution. +1
I have no problems in making the avalon sandbox of the cocoon kernel depend on frozen versions of Avalon Framework and Avalon ECM that didn't change in the last two years.
As long as we agree *never to change it*.
If Leo's are right, it is also possible to make avalon components be exposed "outside" the avalon sandbox without loss of functionality.
I don't see how, but I love to be proven wrong.
But I sand firmly on my position:
+1 on having an avalon sandbox -1 on having the core of the cocoon kernel depend on avalon directly
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
