[
https://issues.apache.org/jira/browse/SLING-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-9806.
---------------------------------
Resolution: Fixed
Fixed in [commit
51f153b|https://github.com/apache/sling-org-apache-sling-commons-johnzon/commit/51f153bffca880081b4a011850e5c3854d37fdd7].
> Export the johnzon.core packages provided by org.apache.johnzon:johnzon-core
> ----------------------------------------------------------------------------
>
> Key: SLING-9806
> URL: https://issues.apache.org/jira/browse/SLING-9806
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Commons Johnzon 1.2.6
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{org.apache.sling.commons.johnzon}} is a wrapper over
> {{org.apache.johnzon:johnzon-core}}, to make sure that the latter works
> correctly in Sling. Even though {{johnzon-core}} is an OSGi bundle, it seems
> that it can still not be deployed as is in Sling, without also deploying
> SPI-Fly - see JOHNZON-108 for context.
> Since other {{johnzon}} bundles (e.g. {{johnzon-mapper}}) could be useful in
> a Sling deployment, the OSGi packages that
> {{org.apache.johnzon:johnzon-core}} exports should be re-exported by
> {{org.apache.sling.commons.johnzon}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
