[
https://issues.apache.org/jira/browse/FELIX-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628688#comment-17628688
]
Carsten Ziegeler edited comment on FELIX-6578 at 11/4/22 6:14 AM:
------------------------------------------------------------------
Changed to jakarta json in
https://github.com/apache/felix-dev/commit/14550ae359750cf986b9bfdee30b12fd75509784
and renamed package in
https://github.com/apache/felix-dev/commit/2afdf46e75e5351762e6b17d4d0c2d83c69a025b
As we want to support running the old and the new version in parallel, we need
to change the packages, therefore I changed from o.a.f.cm.json to
o.a.f.cm.json.io (open for better suggestions, but I wanted to keep cm.json and
didn't want to use something like cm.json2)
was (Author: cziegeler):
Changed to jakarta json in
https://github.com/apache/felix-dev/commit/14550ae359750cf986b9bfdee30b12fd75509784
As we want to support running the old and the new version in parallel, we need
to change the packages, therefore I changed from o.a.f.cm.json to
o.a.f.cm.configuration (open for better suggestions)
> Migrate to jakarta json
> -----------------------
>
> Key: FELIX-6578
> URL: https://issues.apache.org/jira/browse/FELIX-6578
> Project: Felix
> Issue Type: Improvement
> Components: Configuration Admin
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: cm.json-2.0.0
>
>
> The cm.json module is currently using javax.json in its API as well as in its
> implementation.
> We should migrate this code to use the (newer) jakarta.json API instead.
> However, as javax.json is currently used in the API, this will be a breaking
> change to all downstream users.
> Therefore we should make it possible to run the old and the new
> implementation in parallel (including as a library) and also make sure that
> we support / maintain the old implementation as needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
