[BUILD-303] Build on JDK11+ Created: 09/May/18  Updated: 09/Feb/23

Status: Selected
Project: Build
Component/s: Poms
Affects Version/s: POMs 36, BOM 5.7
Fix Version/s: None

Type: Epic Priority: Major
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: java11, junit5, maven
Remaining Estimate: Not Specified
Time Spent: 3.5d
Original Estimate: 2d

Issue Links:
Cloners
clones BUILD-300 Builds failing on JDK9+ due to javax.... Closed
is cloned by BUILD-550 Java Technical update Selected
Relates
relates to BUILD-404 Enable basic JUnit 5 Selected
relation
is related to BUILD-698 Update Guice Closed
is related to BUILD-751 Consider phasing out animal-sniffer m... Open
supersession
supersedes BUILD-309 Java 9–10 runtime compatibility Closed
Template:
Epic Name: Build on JDK11+
Acceptance criteria:
Empty
Date of First Response:
Sprint: Saigon 145, Saigon 146
Team: Foundation

 Description   

Goals

  1. Make sure parent poms provide maven plugins supporting Java 9, 10, 11...
    1. validate through release lifecycle (how we missed the issue with site-plugin last time)
    2. define a migration path such that newer Java versions can be used but class files stay compatible with Java 8 until all dependencies have been migrated.
  2. Find where this triggers compile issues (as in mvn test-compile), without tests
  3. Pave the way for modern test execution
    1. on JDK9+ (more effort, mockito 2 upgrade, etc.); file tickets
    2. using JUnit5, running both new/old tests with both jupiter/vintage engines

Execution

  • 6.2 will remain on java 8
  • Prepare branches on 6.2 with necessary changes for Java 11 (e.g. upgrade to Mockito 2.x) but keep the base version at Java 8.
  • When we do get 6.3 branches then those would build on 11 initially, with 17 coming in a 2nd step
  • Ensure modules still produce class file versions that are compatible with Java 8: keep javaVersion at 8 but build with Java 11 on Jenkins. Start bumping javaVersion to 11 starting with leaf modules once all relevant modules build on Java 11.


 Comments   
Comment by Sang Ngo Huu [ 14/Jun/18 ]

This code reaches the goal, but unit tests are failed, so it cannot be merged. Reopen for further handling

Comment by Mikaël Geljić [ 05/Jul/18 ]

cmeier that seems relevant  hopefully a lombok upgrade should do. Can you file an issue in this epic?

Comment by Christoph Meier [ 05/Jul/18 ]

mgeljic - created, see BUILD-319

Comment by Saimir Gasa [ 19/Oct/18 ]

cmeier, even though the workflow currently allows it an epic should not be closed unless all issues in that epic are closed. Sorry, I don't have a better answer for you short of changing the workflow configuration.

Generated at Sun Feb 11 23:40:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.