[
https://issues.apache.org/jira/browse/OAK-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655106#comment-16655106
]
Robert Munteanu commented on OAK-7851:
--------------------------------------
[~frm], [~mduerig] - FYI
> Inline or remove embedding of Netty jars
> ----------------------------------------
>
> Key: OAK-7851
> URL: https://issues.apache.org/jira/browse/OAK-7851
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Robert Munteanu
> Priority: Major
>
> The {{oak-segment}} jar embeds a number of jars, mostly from Netty:
> {noformat}concurrentlinkedhashmap-lru-1.4.2.jar
> netty-buffer-4.1.14.Final.jar
> netty-codec-4.1.14.Final.jar
> netty-common-4.1.14.Final.jar
> netty-handler-4.1.14.Final.jar
> netty-resolver-4.1.14.Final.jar
> netty-transport-4.1.14.Final.jar{noformat}
> This causes a small performance hit on startup and the jars must be always
> expanded. This is more visible when using the Sling feature launcher as it
> uses references to existing jar files instead of copying them around.
> There is also a space impact, as the embedded jars will be stored both in the
> segment-tar jar _and_ on disk after being copied out.
> Additionally, the visibility of these jar can be controlled with the API
> regions mechanism, to make it clear that they are not mean to be consumed
> outside Oak, so it should be safe to remove the embedding altogether.
> Alternatively, these can be still embedded but also inlined.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
