[
https://issues.apache.org/jira/browse/MCOMPILER-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517711#comment-17517711
]
John Patrick commented on MCOMPILER-489:
----------------------------------------
I know what you are saying, and that is what i'm trying to do, but in practice
I'm fighting either Java, Maven or the IDE.
Are you aware of a working example that handles src/main/java (JDK 1.8) and
src/main/java11 (JDK 11) and src/main/java17 (JDK 17). And also loads in the
latest version of IntelliJ, with the correct source directories being marked as
source directories based upon the value of the "JDK for importer".
Recent changes in IntelliJ appear to parse the pom differently and now I've
some projects that you can't execute unit tests as it parses the pom and thinks
it should be Java 11 but everything is set to Java 1.8.
> User property for multiReleaseOutput
> ------------------------------------
>
> Key: MCOMPILER-489
> URL: https://issues.apache.org/jira/browse/MCOMPILER-489
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Reporter: John Patrick
> Priority: Minor
> Labels: CompilerOptions
>
> Add support so multiReleaseOutput can be provided as a user property.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
