[
https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936995#comment-15936995
]
Stefan Seifert edited comment on SLING-6679 at 3/22/17 7:55 PM:
----------------------------------------------------------------
{quote}
Furthermore, it is a question if we are happy with the requirements pushed on
us by these issues namely:
deploy these bundles and make sure they are loaded before the others via OSGi
bundle startlevel :
org.apache.aries.spifly:org.apache.aries.spifly.dynamic.bundle:1.0.8
org.apache.aries:org.apache.aries.util:1.1.1
org.ow2.asm:asm-all:5.0.4
{quote}
there might be an alternative to simplify the deployment - and we would not
have to wait for the solution of GERONIMO-6560 and JOHNZON-108:
* we create an new bundle embedding {{johnzon-core}} and
{{geronimo-json_1.0_spec}}
* we would not need spifly and it's dependencies because the ServiceLoader can
locate the johnzon implementation in the local classpath of the bundle
* we export javax.json from this bundle
* we need some classloader tweaking code to work around the usage of
ThreadContextClassLoader in the spec jar - but this is hidden from the users of
exported classes
drawback: if a new version of johnzon or the json spec is released we have to
release a new version of this wrapper bundle as well.
was (Author: [email protected]):
{quote}
Furthermore, it is a question if we are happy with the requirements pushed on
us by these issues namely:
deploy these bundles and make sure they are loaded before the others via OSGi
bundle startlevel :
org.apache.aries.spifly:org.apache.aries.spifly.dynamic.bundle:1.0.8
org.apache.aries:org.apache.aries.util:1.1.1
org.ow2.asm:asm-all:5.0.4
{quote}
there might be an alternative to simplify the deployment - and we would not
have to wait for the solution of GERONIMO-6560 and JOHNZON-108:
* we create an new bundle embedding {{johnzon-core}} and
{{geronimo-json_1.0_spec}}
* we would not need spifly and it's dependencies because the ServiceLoader can
locate the johnzon implementation in the local classpath of the bundle
* we export javax.json from this bundle
drawback: if a new version of johnzon or the json spec is released we have to
release a new version of this wrapper bundle as well.
> 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)
