[
https://issues.apache.org/jira/browse/SLING-11718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645180#comment-17645180
]
Carsten Ziegeler commented on SLING-11718:
------------------------------------------
[~kwin] Sooner or later we will have jakarta.json at runtime. As the json
library is an implementation detail of the jcr content loader, I don't think it
is worth the effort to maintain two versions. We should rather go with having
javax.json and jakarta.json at runtime in parallel for the time being. See also
my email to the dev list
> Migrate to Jakarta JSON API
> ---------------------------
>
> Key: SLING-11718
> URL: https://issues.apache.org/jira/browse/SLING-11718
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model, Feature Model Analyser, Maven Plugins and
> Archetypes
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Feature Model Analyser 2.0.0, slingfeature-maven-plugin
> 1.6.10, Feature Diff 0.1.0, JCR ContentLoader 2.5.4, Content-Package to
> Feature Model Converter 1.1.26, Feature Model 2.0.0, Feature Model API
> Regions Extension 2.0.0, Feature Model Launcher 1.2.4
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
