[jira] [Commented] (FELIX-6578) Migrate to jakarta json
[ https://issues.apache.org/jira/browse/FELIX-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628694#comment-17628694 ] Carsten Ziegeler commented on FELIX-6578: - [~laeubi] Thats how its done - we have version 1.x support javax.json and version 2.x supporting jakarta.json - in addition both versions use different package names, so you can run version 1.x and 2.x side by side > 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)
[jira] [Commented] (FELIX-6578) Migrate to jakarta json
[ https://issues.apache.org/jira/browse/FELIX-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628689#comment-17628689 ] Christoph Läubrich commented on FELIX-6578: --- > However, as javax.json is currently used in the API, this will be a breaking > change to all downstream users. Wont this be a goo choice to raise the major version then and (if required) have changes for "old" on a branch instead of maintain two implementations/api interfaces in the same bundle? > 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)
[jira] [Commented] (FELIX-6578) Migrate to jakarta json
[ https://issues.apache.org/jira/browse/FELIX-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628688#comment-17628688 ] Carsten Ziegeler commented on FELIX-6578: - 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)
