[
https://issues.apache.org/jira/browse/MCOMPILER-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MCOMPILER-542:
------------------------------------
Description:
as seen in MJAR-275, JDK patch version in module-info.class is NOT included
only when building with a newer JDK release using "--release" flag, see
[https://github.com/jvm-repo-rebuild/module-info]
we need an issue in JDK to get a proper fix at javac level
and waiting for that, we need a workaround to drop the JDK patch version in
other cases: we'll need to define where is the best place –
m-jar-p?m-compiler-p? other?
was:
as seen in MJAR-275, JDK patch version in module-info.class is not included
only when building with a newer JDK release using "--release" flag, see
https://github.com/jvm-repo-rebuild/module-info
we need an issue in JDK to get a proper fix
and waiting for. that, we need a workaround to drop the JDK patch version in
other cases: we'll need to define were is the best place --
m-jar-p?m-compiler-p? other?
> clean JDK patch version in module-info.class
> --------------------------------------------
>
> Key: MCOMPILER-542
> URL: https://issues.apache.org/jira/browse/MCOMPILER-542
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Affects Versions: 3.11.0
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.12.0
>
>
> as seen in MJAR-275, JDK patch version in module-info.class is NOT included
> only when building with a newer JDK release using "--release" flag, see
> [https://github.com/jvm-repo-rebuild/module-info]
> we need an issue in JDK to get a proper fix at javac level
> and waiting for that, we need a workaround to drop the JDK patch version in
> other cases: we'll need to define where is the best place –
> m-jar-p?m-compiler-p? other?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
