[
https://issues.apache.org/jira/browse/MPOM-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803264#comment-17803264
]
Herve Boutemy edited comment on MPOM-449 at 1/11/24 9:25 AM:
-------------------------------------------------------------
very good idea: this is supported since Java 5, we can forget about this "1."
that was necessary (by javac, I don't know if m-compiler-p was really checking
the format) only until Java 1.4...
https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javac.html
was (Author: hboutemy):
very good idea: this is supported since Java 5, we can forget about this "1."
that was necessary (by javac) only until Java 1.4...
https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javac.html
> Remove the leading "1." from source/target properties
> -----------------------------------------------------
>
> Key: MPOM-449
> URL: https://issues.apache.org/jira/browse/MPOM-449
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Affects Versions: MAVEN-41
> Reporter: Tamas Cservenak
> Assignee: Sylwester Lachiewicz
> Priority: Major
> Fix For: MAVEN-42
>
>
> The parent 41 has these lines:
> {noformat}
> <maven.compiler.source>1.${javaVersion}</maven.compiler.source>
> <maven.compiler.target>1.${javaVersion}</maven.compiler.target> {noformat}
> This makes any Java above 9 defunct (and we do not go below 8, so it works
> for only two versions). If you try to use 11, 17 or oh my god 21, you end up
> with "1.11", "1.17" and "1.21" subsequently. While for javac this is not a
> biggie (it will ignore this if release set, and hopefully is), but
> reporting/site/whatever craps out badly on this.
> Remove the prefix "1.", and let those on 8 use 1.8 instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
