cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [RT] Building ECM++ for 2.2
Date Mon, 18 Oct 2004 13:37:24 GMT
Carsten Ziegeler wrote:


>Adding new things on top of an old one provides a smooth migration
>path, as you can still use the old ones and one or two additional
>If you have a compatibility layer this most often means that you
>can either use this layer or the new functionality. So there isn't
>a smooth migration path in this case.

The purpose of a compatibility layer is to be able to use _both_ old and 
new features at the same time, otherwise it would be rather useless.

>Now, we don't have to add new functionality to the old one, but
>it is an option. And with this approach we are getting more
>independent from Avalon/Excalibur without loosing anything.

Yup. That's why I have nothing about forking ECM in our repo. But I hope 
to prove it's actually even not necessary.


Sylvain Wallez                                  Anyware Technologies 
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }

View raw message