On 17/08/16 14:13, Christian Schneider wrote:
On 17.08.2016 15:08, Sergey Beryozkin wrote:
Letting the old classes extend the new ones is also not possible as core
can not depend on the logging feature jar.
Then we need to solve it differently. Move the ext code into the core
and have the ext interceptors and feature simply extend that code
That will mean a gentler migration effort.
I do not agree. In a major version we should remove old stuff. The time
to migrate is in 3.1 where both logging features exist.
So people can gradually move to the new logging. Then when they complete
the migration they switch to CXF 4 without any changes. This is why I
try to create new functionality in a minor version and remove the old
one in a major version.
Of course this can mean that a major version has 0 new features but that
is exactly the purpose outside of marketing.
You keep operating with some academic terms which have little do with
the practicalities.
Imagine what will happen if you get rid of the core package as far as
the external tooling and 3rd party use of this one of the most often
used CXF feature.
Likewise I'm -1 on removing the core code from 3.2.0. Lets have 2 sets
of interceptors
Sergey
Christian
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
