[
https://issues.apache.org/jira/browse/MCOMPILER-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479603#comment-16479603
]
Mike Drob commented on MCOMPILER-323:
-------------------------------------
Mapping the source directories to unique output directories and compiling them
in a separate pass makes sense to me (as described in his next blog post).
bq. Creating mrjars will be complex and should be avoided
Agree with the first part. Disagree that it needs to be avoided...
That's why folks are coming out and asking for tooling for it. We don't have to
wait for the unit testing to get easy, or IDE support to get there before we
figure out how to support MR jars. If we make MR jars possible, then I believe
that surefire executions and IntelliJ integration and all the other missing
pieces will follow eventually. As is right now, nobody knows how to take the
first step.
> Support multi-release jars
> --------------------------
>
> Key: MCOMPILER-323
> URL: https://issues.apache.org/jira/browse/MCOMPILER-323
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Reporter: Mike Drob
> Priority: Major
>
> Java 9 allows for JRE version specific code in the form of "multi-release
> jars"
> Older JREs will treat them as normal jars, while newer JREs will load the
> appropriate specific classes. AFAICT, maven does not currently support this.
> Compiler plugin should automatically detect when there are multiple source
> levels and set MRJAR=True in the manifest.
> Source directories could potentially be src/main/java, src/main/java9,
> src/main/java10, etc. These probably need to be configurable as well, or some
> deeper discussion about what makes sense and is intuitive for users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
