[SLING-8728] Make sure Sling modules can be built with Java 8, Java 11 and the latest release

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Tooling
• Assignee: Unassigned
• Reporter: Radu Cotescu
• Created: 20/Sep/19 14:15
• Updated: 28/Sep/21 16:05

Description

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/.

Issue Links

• is blocked by: SLING-9948 Jenkins: Parallelize steps of pipeline
• is blocked by: SLING-8734 Perform migration of modules to parent 35 (or newer)
• is related to: SLING-9839 Jenkins: Sonarcloud analysis with Java 11
• is related to: SLING-8199 Allow building for Java 10, 11 and 12
• is related to: SLING-8285 Update plugins to work with Java11+

Sub-Tasks

• Generate list of modules to migrate to sling parent 35 (or newer): Open
• Update default JVMs in Jenkins tooling to reference 8,11, and latest Java: Open