[SLING-11718] Migrate to Jakarta JSON API

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Feature Model Analyser 2.0.0, OSGi Feature Maven Plugin 1.7.0, Feature Model Diff Tool 0.1.0, JCR ContentLoader 2.6.0, Content-Package to Feature Model Converter 1.3.0, Feature Model 2.0.0, Feature Model API Regions Extension 2.0.0, Feature Model Launcher 1.3.0
• Component/s: Feature Model, Feature Model Analyser, Maven Plugins and Archetypes
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 06/Dec/22 05:34
• Updated: 25/Apr/23 12:27
• Resolved: 23/Dec/22 08:09

Description

Starting with JEE 9 the package names for the enterprise APIs changed from javax.* to jakarta.* which means that we will benefit from updates to those APIs only if we make the move.

For the feature model and the related tooling, it should be fairly easy to do this move as this code is usually only used at tool time but not at application runtime.

We can 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.

Issue Links

• is related to: SLING-11836 Add Jakarta JSON support to the Sling Starter
• links to: GitHub Pull Request #153