Okay, I'm going to counter this argument. The new content parser is a different bundle, a different import, then the old content parser.
the old content parser package is org.apache.sling.jcr.contentparser That can and will co-exist with org.apache.sling.contentparser My opinion is that the old API will need to be deprecated for the new one. And semantically the new one should be 1.0.0 -- Jason On Fri, Jul 19, 2019, at 11:51 AM, Radu Cotescu wrote: > Hi Stefan, > > > On 19 Jul 2019, at 15:20, Stefan Seifert <[email protected]> wrote: > > > > 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 > > > > Ok, then let’s start everything here with version 2.0.0 - all bundle > versions, all exported packages. > > Cheers, > Radu
