[BUILD-812] Remove javaVersionWithoutInitialOne property Created: 25/May/22  Updated: 24/Oct/23

Status: Accepted
Project: Build
Component/s: Poms
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Unresolved Votes: 0
Labels: foundation_team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon BUILD-751 Consider phasing out animal-sniffer m... Open
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Build on Java 17
Team: Foundation

 Description   

Remove the javaVersionWithoutInitialOne hack/property that was introduced to allow specifying java versions as either 1.8 or 8:

It's not used in too many places: see the super-pom, and going forward I'd like the compiler plugin to use the javaVersion straight, which would mean a few things:

  • force all 6.2 modules to change <javaVersion>1.8</javaVersion> to <javaVersion>8</javaVersion>, breaking change
  • review other usages of javaVersion to ensure they accept 8, or turn the situation around: add the 1.${javaVersion} specifically in the compiler-jdk8 profile.
    • if building with JDK8, we can't build for newer versions anyway. But do we want to escape the chances of it resolving to 1.1.8 to not make it a breaking change then?
  • javadoc plugin might need an update actually, to also use the <release> property instead of source accordingly.
  • We could use the require property rule of the Maven enforce plugin to enforce the accepted format of Java version numbers.


 Comments   
Comment by Michael Duerig [ 29/Jun/22 ]

Turns out that the javaVersionWithoutInitialOne property is still used for self testing the animal sniffer with Java 1.7. I make this ticket a dependency of BUILD-751 thus.

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