i think the bundle users will not be really aware oft the removal of the tiny "jcr" part in the package name, for them it's only "the content parser". and if the new version after 1.2.6 is 1.0.0 has the same features as 1.2.6 but a different API, this gets very puzzling.
stefan >-----Original Message----- >From: Radu Cotescu [mailto:[email protected]] >Sent: Friday, July 19, 2019 3:17 PM >To: Sling Dev >Subject: Re: [org.apache.sling.jcr.contentparser] can we decouple it from >JCR? > >Hi Stefan, > >> On 19 Jul 2019, at 12:36, Stefan Seifert <[email protected]> wrote: >> >> in my pov the new modules should get version 2.0.0 as start version, as >they are a successor of the old content parser with the same features, just >bundled in a new way. > >I know it’s just a number, but does it really make sense? We anyways >changed the package name so consumers of the new API will have to perform a >minor refactoring when migrating from the previous one. > >Thanks, >Radu
