You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/10/12 12:05:00 UTC

[jira] [Closed] (SLING-9806) Export the johnzon.core packages provided by org.apache.johnzon:johnzon-core

     [ https://issues.apache.org/jira/browse/SLING-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu closed SLING-9806.
-------------------------------

> 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: 1h 20m
>  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)