[
https://issues.apache.org/jira/browse/SLING-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058116#comment-18058116
]
Stefan Seifert commented on SLING-13104:
----------------------------------------
bq. I'm not sure how not updating to the latest Oak helps.
managing all the dependencies for the mocks and all downstream projects with
the wide range of different sets of dependencies we have to support (e.g. AEM
6.5, 6.6, AEMaaCS) is quite a delicate puzzle. i'm currently testing it
downstream with conservatively only updating to 1.68.0. i want to make sure we
are not using any newer oak features than the version we are defining here, to
ensure compatibility with all downstream projects, where the actual oak version
that is used in usually controlled by the project the unit tests are run in -
think of AEM 6.5 with oak 1.22.x. so this is already a compromise.
bq. Note that oak-jackrabbit-api had extensions since 1.68.0; does that matter
for mocking?
so far i've not encountered any problem
bq. Oak will switch to Java 17 in the release after the next one (ca 10 weeks
from now).
that's fine in general, as sling is also going to java 17 as minimum with the
jakarta servlet update. for jcr-mock, we should stick for older oak versions
for a longer time for the reasons outlined above.
> sling-mock, jcr-mock: Update to Oak 1.68.0 / JR 2.22.2
> ------------------------------------------------------
>
> Key: SLING-13104
> URL: https://issues.apache.org/jira/browse/SLING-13104
> Project: Sling
> Issue Type: Task
> Components: Testing
> Reporter: Julian Reschke
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing JCR Mock 1.8.0, Testing Sling Mock 3.6.0,
> Testing Sling Mock 4.0.4
>
>
> sling-org-apache-sling-testing-jcr-mock: has Guava dependency through Oak
> dependency to 1.22.x.
> We'd need to update to a version that does not depend on Guava (latest would
> be 1.90.0)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
