[
https://issues.apache.org/jira/browse/SLING-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302683#comment-17302683
]
A. J. David Bosschaert commented on SLING-10092:
------------------------------------------------
Hi [~cziegeler] - if I want to read a configuration from a feature model, I
could also just parse the whole feature and read it from that? Maybe it's a
little bit less efficient, but not sure if it makes a big difference.
I don't see these classes being used anywhere, but I guess they could be used
somewhere as they are exported API, so removing them would be backward
incompatible in theory. So maybe for that reason we should keep them...
> 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)
