+1 with the latest changes from https://github.com/apache/sling-whiteboard/pull/47
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. stefan >-----Original Message----- >From: Radu Cotescu [mailto:[email protected]] >Sent: Thursday, July 4, 2019 5:00 PM >To: Sling Dev >Cc: Stefan Seifert >Subject: [org.apache.sling.jcr.contentparser] can we decouple it from JCR? > >Hi Stefan, > >I do know that the module has JCR in its name, but do you think that we >could make the JCR stuff optional? I’d really like to reuse this module to >parse JSON into Sling resource trees, but I’d like the JCR dependencies to >be optional, since in my experimental setup I use a different resource >provider. > >Thanks, >Radu
