[
https://issues.apache.org/jira/browse/SLING-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-12208.
------------------------------------
Resolution: Fixed
*
[https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/c9cf4bc35580394dcd2327cc25a3baf479647de3]
*
[https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/commit/2ff8736b466ef13c449adb0bb3df125cd9430e63]
*
[https://github.com/apache/sling-org-apache-sling-testing-resourceresolver-mock/commit/34db5a5a8ad48adb7e041a135af6cc239cd65fe6]
*
[https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/39a864df8893025de7db92cc55528d0fd0fda160]
*
[https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/commit/83747eff96ad0804e5b772257edeb010317a8841]
> sling/jcr/osgi/resourceresolver-mock: Update Dependencies to 2023
> -----------------------------------------------------------------
>
> Key: SLING-12208
> URL: https://issues.apache.org/jira/browse/SLING-12208
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing Sling Mock Oak 3.1.12-1.44.0, Testing
> ResourceResolver Mock 1.4.6, Testing OSGi Mock 3.4.2, Testing Sling Mock
> 3.4.18, Testing JCR Mock 1.6.14
>
>
> every 1-2 years we update the dependencies of sling-mock and related mock
> modules to a new "baseline" of dependencies. as sling-mock is used in a lot
> of user projects with very different context (applications, deployment
> target) we try to be as backwards-compatible as possible but dropping out
> older versions from time to time.
> the baseline we target for this ticket is:
> [https://repo1.maven.org/maven2/io/wcm/maven/io.wcm.maven.aem-dependencies/6.5.17.0001/io.wcm.maven.aem-dependencies-6.5.17.0001.pom]
> several dependencies from this POM esp. from Sling and Oak are not the latest
> version from mid 2023, but it's a consistent baseline that is still used in a
> lot of projects.
> the goal is to stick to this baseline for the next 1-2 years and only deviate
> from it with a good reason. such a reason might be security warnings in
> artifact scanners - but only if it deviates not too much or in a potential
> risky way from this baseline.
> the goal is that all mock code that is written sticks to this baseline.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
