ciao julian the plan sound reasonable to me.... it's overdue that we get this done, so any progress is good IMHO.
kind regards angela ________________________________ From: Julian Reschke <julian.resc...@gmx.de> Sent: Monday, February 6, 2023 11:51 To: oak-dev@jackrabbit.apache.org <oak-dev@jackrabbit.apache.org> Subject: OAK-7182: Make it possible to update Guava Hi, I just updated the ticket with a proposed timeline (see <https://issues.apache.org/jira/browse/OAK-7182?focusedCommentId=17684580&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17684580>): OAK 1.48.0 (January 2023) bump up default logging levels for deprecated APIs to "warn" (OAK-10047) OAK 1.50.0 (March 2023) switch to Java 11 und use "forRemoval" deprecations for APIs exposing Guava (OAK-10007) bump up default logging levels for deprecated APIs to "error" (OAK-10086) OAK 1.52.0 (May 2023) introduce wrapped Guava project for Oak-internal use (OAK-9989) OAK 1.54.0 remove deprecated APIs exposing Guava ...feedback appreciated. Best regards, Julian