Description
Recently, as new Java versions are pushed out more aggressively (with Java 21 out this autumn), seemingly it became normal that users developing Maven plugins (and components used by those plugins) using bytecode level that is Java14+.
But alas, Maven 3.9.x line uses Sisu 0.3.5 that is capable to glean bytecode only up to Java 14. Components having higher version bytecode are silently skipped by Sisu (no output about this, only at Sisu DEBUG level not emitted by default).
Hence, it would make sense to up Sisu version to at least 0.9.0.M2 in Maven 3.9.x as well, that would allow use of JSR330 components using bytecode more recent that Java 14 is, up to 19.
Attachments
Issue Links
- causes
-
MNG-8227 Cleanup after Sisu upgrade
- Open
- is related to
-
SPARK-46335 Upgrade Maven to 3.9.6 for MNG-7913
- Resolved
-
MNG-7587 Update Sisu to a version supporting at least Java 17
- Closed
- relates to
-
MENFORCER-473 Custom Rules are not processed with Java 17
- Open
- links to