> On Feb 21, 2017, at 11:53 AM, Raymond Auge <[email protected]> wrote: > > Hello everyone, > > This is my first post to the list. So thank you in advance for all your > hard work and very good product. > > However, I have a question about semantic versioning of CXF. > > In our project we are using CXF (piecemeal). > > However when we upgraded our dependency from 3.0.3 to 3.1.9 we encountered > MAJOR api changes while baselining.
What kind of major changes? User code should rebuild/re-compile without problem when moving from 3.0.x to 3.1.x. > It seems that there are many semantically invalid changes on this apparent > _minor_ release. I wondered if the CXF project knows that some changes are > not semantically correct or was simply an oversight? > > Would the CXF project entertain adding baseline checks to the build to > assert semantic versioning? Probably not. The semantic versioning that we care about is if apps written to JAX-WS and/or JAX-RS and use the “normal” configuration mechanisms (spring/blueprint) will re-compile and run without modification. Any API changes within CXF modules or between them is not something we worry about. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
