[
https://issues.apache.org/jira/browse/SLING-12287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-12287.
------------------------------------
Resolution: Fixed
* 4.x: (master):
[https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/commit/d4f0388ac9cf592a218230ee01cf14a6c3a93463]
* 3.2.x:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/commit/edf70e21c3e06b9e4960d99332669050727c7251
> sling-mock-oak: Update to Oak 1.60 and provide separate 1.22 release
> --------------------------------------------------------------------
>
> Key: SLING-12287
> URL: https://issues.apache.org/jira/browse/SLING-12287
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing Sling Mock Oak 3.2.0-1.22.15, Testing Sling Mock
> Oak 4.0.0-1.60.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
