Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
following the discussion with reschke in SLING-12266 we should move away from oak 1.44 which is quite outdated. however, we need to ensure to keep compatibility with the old 1.22.x version range to support all sorts of projects using the mocks.
a solution might be to switch to a recent version of oak in the POM, and create dedicated ITs to test against this and older 1.22.x versions to ensure compatibility.
the benefit is, that all projects that are "just using" sling-mock-oak without thinking about the dependency management (e.g. not using something like https://wcm.io/tooling/maven/aem-dependencies.html) will get the latest version which is better supported.
Attachments
Issue Links
- relates to
-
SLING-12266 Cache initial repository state to improve JCR_OAK performance
- Closed
- links to