[SLING-12208] sling/jcr/osgi/resourceresolver-mock: Update Dependencies to 2023

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Testing JCR Mock 1.6.14, Testing Sling Mock Oak 3.2.0-1.22.15, Testing ResourceResolver Mock 1.4.6, Testing OSGi Mock 3.4.2, Testing Sling Mock 3.4.18, Testing Sling Mock Oak 4.0.0-1.62.0
• Component/s: Testing
• Assignee: Stefan Seifert
• Reporter: Stefan Seifert
• Created: 21/Dec/23 10:47
• Updated: 17/Apr/24 13:56
• Resolved: 21/Dec/23 11:55

Description

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.

Issue Links

• is related to: SLING-12282 Content Parser: Update Dependencies to 2023
• relates to: SLING-11295 sling/jcr/osgi/resourceresolver-mock: Update Dependencies to 2020
• relates to: SLING-12144 Bump JUnit, Mockito, Commons Lang dependencies to latest in sling/osgi/jcr/resourceresolver-mock
• links to: GitHub Pull Request #10
• links to: GitHub Pull Request #14
• links to: GitHub Pull Request #34
• links to: GitHub Pull Request #36
• links to: GitHub Pull Request #39