[
https://issues.apache.org/jira/browse/MNG-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-7913:
---------------------------------
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.
was:
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.
> Upgrade Sisu version
> --------------------
>
> Key: MNG-7913
> URL: https://issues.apache.org/jira/browse/MNG-7913
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.6
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
