stefanseifert commented on PR #15: URL: https://github.com/apache/sling-org-apache-sling-servlet-helpers/pull/15#issuecomment-2602945095
yes, this was the right pointer. i now understand paxexam a bit more. first of all, the version of sling.engine that is defined in the pom here has nothing to do with the version that is used in the osgi context of paxexam - unless you specfiy it, its the versions defined here https://github.com/apache/sling-org-apache-sling-testing-paxexam/blob/org.apache.sling.testing.paxexam-4.0.0/src/main/java/org/apache/sling/testing/paxexam/SlingVersionResolver.java and this engine version is too old (there is the 2.9.2) then we depend on here. as described here https://sling.apache.org/documentation/development/testing-paxexam.html it's possible to define different versions to be used by deployed to the osgi container, but this quickly gets out of hand. i managed to use the project version of sling.api and sling.engine, but that required to update resourceresolver and servlets.resolver as well. i stopped when i had to provide jakarta.json as well. so either we provide a updated sling paxexam with more recent sling version included (but with https://issues.apache.org/jira/browse/SLING-12577 that list of versions was removed altogether), or stick with the security warning and the old engine dependency here. or remove the paxexam tests... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
