Hi Carsten, On Tue, 2022-11-29 at 09:22 +0100, Carsten Ziegeler wrote: > Hi, > > as you might know, starting with JEE 9 the package names changed from > javax.* to jakarta.* which means that we will benefit from updates to > those APIs only if we make the move. > > This thread is *not* about moving the whole of Sling over, but just > for > the feature model and the related tooling. This should be less > painful > as usually this code is not used as OSGi bundles at runtime. If > someone > wants to discuss how we should handle Sling itself (mostly the > servlet > api), please start a new thread. > > For the feature model and the tooling around it (including maven > plugins > etc.) I suggest we simply replace javax.json with jakarta.json and do > new releases of everything involved with a new major version. As we > are > currently using javax.json in parts of the API, this will be a > breaking > change, therefore the major version update. > > As we are talking about tooling here and as we can basically update > all > the relevant tooling in one step, I think it is ok to go this way and > we > can avoid thinking about a compatible migration path.
Overall sounds good to me. The only problematic area that I see is the cpconverter, as that ends up embedded in various tools. Since it's a one-off, I hope it will not be problematic. Thanks, Robert
