[
https://issues.apache.org/jira/browse/MCOMPILER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207493#comment-17207493
]
Hudson commented on MCOMPILER-275:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-compiler-plugin » master
#16
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/16/
> Handle separate compilation of module-info.java
> -----------------------------------------------
>
> Key: MCOMPILER-275
> URL: https://issues.apache.org/jira/browse/MCOMPILER-275
> Project: Maven Compiler Plugin
> Issue Type: New Feature
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Attachments: mcompiler-275.patch
>
>
> When you want to add a module-info.java file to your project AND want your
> code to be compatible with older java version, then you need to call
> {{javac}} twice.
> To prevent all kinds of magic for selecting the right files to compile with
> the right version of Java it is probably better to just have a separate
> folder for it, e.g. {{src/main/jigsaw}}. I'd prefer to call it 'jigsaw'
> instead of java9, so it'll still makes sense once we're at java16
> On the jigsaw mailinglist they actually expect the module-info file to be in
> the {{src/main/java}} as well. Intuition of users might indeed be to simply
> put it there and let Maven handle it. That should be possible, but it also
> depends if IDEs can handle this too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
