[
https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942467#comment-15942467
]
Karl Pauls commented on SLING-6679:
-----------------------------------
I think we are getting closer. As far as I can see we have the necessary
bundles converted. However, I didn't run all test yet. In that regard, to make
it easer to test the changes in general and be able to get the integration
tests to run, I created SLING-6713 which updates the provisioning with the
SNAPSHOT versions of the bundles from the other subtasks and swaps commons.json
with commons.johnzon.
In other words, if one does apply all the patches from the sub-issues, builds
the bundles, and builds a new launchpad the system comes up with all bundles
resolved and reachable via the browser.
I will start looking into getting the integration tests to run next.
> Replace usage of org.apache.sling.commons.json.*
> ------------------------------------------------
>
> Key: SLING-6679
> URL: https://issues.apache.org/jira/browse/SLING-6679
> Project: Sling
> Issue Type: Improvement
> Reporter: Karl Pauls
> Assignee: Karl Pauls
>
> Following the deprecation of org.apache.sling.commons.json (SLING-6536) we
> need to replace its usage everywhere else (at least if we want to be able to
> release other modules that depend on it).
> This is the umbrella issue for getting this done. The idea is to create
> sub-issues with patches for individual components, review the patches, and
> when all are done: close this issue.
> General discussions and problems should go to this issue and specific ones on
> the sub-issue in question.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
