[
https://issues.apache.org/jira/browse/SLING-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302693#comment-17302693
]
Carsten Ziegeler commented on SLING-10092:
------------------------------------------
[~davidb] The use cases are different:
- you have a feature model and want to create a configuration resource for the
OSGi configurator. You can do that with cm.json but then you need to write the
code that is currently in ConfigurationJSONWriter
- And ConfigurationJSONReader is actually the reverse use case. You have an
OSGi configuration resource, and want to use it within a feature model
(programmatically). Again, you can use cm.json but that requires a little bit
of code
For those use cases these classes are pretty useful
> Deprecate ConfigurationJSONReader and ConfigurationJSONWriter
> -------------------------------------------------------------
>
> Key: SLING-10092
> URL: https://issues.apache.org/jira/browse/SLING-10092
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Affects Versions: Feature Model 1.2.18
> Reporter: A. J. David Bosschaert
> Priority: Major
> Fix For: Feature Model 1.2.22
>
>
> These 2 classes in the core feature model in the
> org.apache.sling.feature.io.json package are replaced by cm.json and should
> therefore be deprecated and removed in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
