I raised https://issues.apache.org/jira/browse/SLING-12952 for tracking this.
> On 26. Sep 2025, at 14:04, Konrad Windszus <[email protected]> wrote: > > Hi Robert, > Thanks for the input. > Should we manage the minimum versions required in Sling Bundle Parent (with a > property which can be overwritten if necessary)? > Konrad > >> On 25. Sep 2025, at 16:36, Robert Munteanu <[email protected]> wrote: >> >> On Thu, 2025-09-25 at 12:31 +0200, Konrad Windszus wrote: >>> Which Oak version is a reasonable compromise to use a baseline which >>> - runs on all recent Java LTS versions (at least Java 21) >>> - is still compatible with older distributions? >>> >>> Oak itself only maintains 1.22 as LTS version and the newest one. >>> >>> Unfortunately Maven/IDE integrations don’t allow to fully decouple >>> test and compile dependencies >>> (https://maven.apache.org/surefire/maven-surefire-plugin/examples/con >>> figuring-classpath.html) which forces us to balance IT with runtime >>> requirements in this case. Although there are some workarounds >>> provided those are not understood by IDEs and hard to maintain, >>> therefore I would strongly suggest find a middle ground here and use >>> compile time dependencies still working with recent Oak versions. >> >> I agree we should use a recent Oak version and forget about those that >> don't work on Java 21. >> >> If 1.62.0 works we could start with that as it's already being used in >> the mocks. >> >> It may happen as a side-effect that we will have higher requirements >> because of e.g. newer jackrabbit-jcr-commons but I think we can live >> with that. >> >> Thanks, >> Robert >> > >
