Carsten Ziegeler wrote:
<snip/>
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
ones.
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
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
