On Tue, Apr 25, 2017 at 1:53 PM, Stefan Seifert <sseif...@pro-vision.de> wrote: > >>Do we need this util class in the api at all? (I have no idea, but just >>asking the obvious question) > > perhaps not, but a lot of existing code outside there may use it. and > providing an alternative on javax.json is perhaps easier to migrate to than > completely removing it. > > >>I understand that for semantic versioning we have to increase the major >>version of the api. How do we deal with all the code out there currently >>importing 1.x? Can we find a way that does not require everyone to >>change her code? > > if other classes except JSONUtil are used it's a drop-in replacement, just a > recompile against the latest package version is needed (or a relaxed import > statement for both major versions). but this still is of course a complex > tasks if a lot of bundles depend on the old major version. > > we might change the symbolic name of the new xss bundle to allow parallel > deployment of old and new implementation.
Well, technically, that isn't needed from an OSGi perspective but it might make things easier for Sling users given how things currently work wrt. the installer etc. regards, Karl > stefan > -- Karl Pauls karlpa...@gmail.com
