[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779194#comment-16779194
]
Julian Sedding commented on OAK-7182:
-------------------------------------
bq. That would be similar to having an oak bundle that just wraps & shades
Guava, right?
Yes, except you wouldn't shade Guava but deploy it instead. Thus Oak could stay
slim. Furthermore, embedding (and not exporting) Guava may lead to class loader
issues for cases where Guava classes are used in API signatures. I.e. class
GuavaA inside Oak would be loaded from embedded/shaded classes, whereas client
bundles may load it from another buzndle. Thus GuavaA != GuavaA as far as Java
is concerned, because their class loaders mismatch.
bq. ... biggest roadblock ...
Agreed. That's were the most urgent action is needed and probably the biggest
effort.
> Make it possible to update Guava
> --------------------------------
>
> Key: OAK-7182
> URL: https://issues.apache.org/jira/browse/OAK-7182
> Project: Jackrabbit Oak
> Issue Type: Wish
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff,
> OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff,
> guava.diff
>
>
> We currently rely on Guava 15, and this affects all users of Oak because they
> essentially need to use the same version.
> This is an overall issue to investigate what would need to be done in Oak in
> order to make updates possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
