[
https://issues.apache.org/jira/browse/SLING-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000703#comment-17000703
]
Bertrand Delacretaz commented on SLING-8728:
--------------------------------------------
There's an example using multiple JDKs for testing at
https://github.com/apache/sling-org-apache-sling-launchpad-testing/blob/master/.sling-module.json
> Make sure Sling modules can be built with Java 8, Java 11 and the latest
> release
> --------------------------------------------------------------------------------
>
> Key: SLING-8728
> URL: https://issues.apache.org/jira/browse/SLING-8728
> Project: Sling
> Issue Type: Task
> Components: Tooling
> Reporter: Radu Cotescu
> Priority: Major
>
> While Sling code can run on Java 8 and Java 11, we should validate that our
> modules can also be built using:
> * Java 8
> * Java 11
> * latest Java release
> This would reduce the effort of supporting newer LTS Java versions, by
> incrementally adapting our build process / code.
> Before enabling the jobs in Jenkins, we should make sure that all modules use
> {{sling}} or {{sling-bundle-parent}} POMs version 35 or greater.
> For some modules this requires migrating to the new OSGi annotations. A good
> guide for that is
> https://blog.osoco.de/2016/05/migrating-from-the-apache-felix-scr-annotations-to-the-osgi-declarative-services-annotations/.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
