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

Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2020/09/18 23:45:00 UTC

[jira] [Commented] (SLING-8041) Inline kxml2 in the JCR Contentloader

    [ https://issues.apache.org/jira/browse/SLING-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198590#comment-17198590 ] 

Eric Norman commented on SLING-8041:
------------------------------------

It looks like this was already done for the 2.3.0 release?  If there are no objections in a few days I intend to mark this one as resolved.

> Inline kxml2 in the JCR Contentloader
> -------------------------------------
>
>                 Key: SLING-8041
>                 URL: https://issues.apache.org/jira/browse/SLING-8041
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR ContentLoader 2.2.6
>            Reporter: Karl Pauls
>            Priority: Minor
>             Fix For: JCR ContentLoader 2.4.0
>
>
> It would be nice if we could inline the embedded kxml2 jar in the contentloader to avoid extracting it into the framework cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)