[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433431#comment-17433431
]
Julian Reschke commented on OAK-7182:
-------------------------------------
bq. Julian Reschke I was trying to understand what needs to be done for
OAK-8717. I've seen that it does already contain a patch, it hasn't been merged
because it was only part of the required work? Or should I completely ignore
its content?
It wasn't merged back then because downstream users of Oak were not ready for
the binary incompatibilty.
The patch itself probably is still good, but we'll have to check that in the
meantime no new Guava dependencies have been added to the API.
bq. One more thing, if I may: some changes were made to the modules pom.xml.
Most of the time was about the Embed-Dependency of the maven-bundle-plugin.
That I find it hard to understand, and I feel it goes beyond my current
knowledge of the code.
AFAIR, this was so we could inline the code that extends Guava's cache, so we
don't need to export it.
> 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
> 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
(v8.3.4#803005)
