[
https://issues.apache.org/jira/browse/MCOMPILER-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481458#comment-15481458
]
Karl Heinz Marbaise commented on MCOMPILER-277:
-----------------------------------------------
This is not a feature of the plugin it's a feature of the underlying JDK (or to
be more accurate of the javac) which support target/source option with all the
drawbacks it has...If you need to support different JDK's there is not really
an other way to support that via installing the needed JDK's. Using toolchains
is the correct way to handle this in Maven.
If you have a server that needs to support different JDK's the best way is to
install the needed JDK's...and configure Toolchains correctly than
maven-compiler-plugin will use the appropriate JDK (javac) and it will work...
> Compilationg error while compiling for 1.6 using JDK 1.8
> --------------------------------------------------------
>
> Key: MCOMPILER-277
> URL: https://issues.apache.org/jira/browse/MCOMPILER-277
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.3, 3.5.1
> Environment: Maven 3.2.5. JDK 1.8.
> Reporter: Yoram Michaeli
>
> I have JDK 8 (Java version: 1.8.0_91, vendor: Oracle Corporation) installed
> with Maven 3.2.5 and the maven-compiler-plugin is set for source and target
> version 1.6.
> I'm getting the following compilation error:xxx is not abstract and does not
> override abstract method getParentLogger() in javax.sql.CommonDataSource
> Switching the environment (PATH and JAVA_HOME) to work with JDK 6 (Java
> version: 1.6.0_45, vendor: Sun Microsystems Inc.) compiles OK.
> Seems to me that the plugin is not really compiles for 1.6.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
