[
https://issues.apache.org/jira/browse/MCOMPILER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195334#comment-17195334
]
Arend v. Reinersdorff commented on MCOMPILER-376:
-------------------------------------------------
In my experience, the Java version is set explicitly in every Maven project. I
think this is because of two reasons:
1) The default Java version of 1.6 is quite old. Very few projects are still on
Java 1.6. [~singingbush]'s suggestion would fix this for many projects.
2) The default Java version is not obvious. If the Java version is not set
explicitly, one has to look for the version of the Maven Compiler Plugin and
check which default Java version it uses. If the version of the Maven Compiler
Plugin is not set in the Pom, one has to find out its default version first.
I wonder if it wouldn't be better to force the user to set the Java version
explicitly.
> Change default source/target to 1.7 (new minimum for JDK 12)
> ------------------------------------------------------------
>
> Key: MCOMPILER-376
> URL: https://issues.apache.org/jira/browse/MCOMPILER-376
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
>
> With the statement "It must be possible to build a Hello World application
> with the latest JDK + latest Maven + minimum pom" the default value for
> source+target must be lifted to 1.7
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
