Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
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/.
Attachments
Issue Links
- is blocked by
-
SLING-9948 Jenkins: Parallelize steps of pipeline
- Resolved
-
SLING-8734 Perform migration of modules to parent 35 (or newer)
- Open
- is related to
-
SLING-9839 Jenkins: Sonarcloud analysis with Java 11
- Resolved
-
SLING-8199 Allow building for Java 10, 11 and 12
- Closed
-
SLING-8285 Update plugins to work with Java11+
- Closed
1.
|
Generate list of modules to migrate to sling parent 35 (or newer) | Open | Unassigned | |
2.
|
Update default JVMs in Jenkins tooling to reference 8,11, and latest Java | Open | Unassigned |