[
https://issues.apache.org/jira/browse/MCOMPILER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605266#comment-16605266
]
Charles Oliver Nutter commented on MCOMPILER-361:
-------------------------------------------------
Another gist showing that the command-line that maven-compiler-plugin generates
does indeed fail:
[https://gist.github.com/headius/b857958911cd8cf00d353aba36862761]
I've asked @jddarcy on Twitter for clarification as to whether this should be
expected to work, since he said this should be working in a reply to my ranting.
> module-info in multi-release jar is not picked up by compile
> ------------------------------------------------------------
>
> Key: MCOMPILER-361
> URL: https://issues.apache.org/jira/browse/MCOMPILER-361
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.8.0
> Reporter: Charles Oliver Nutter
> Priority: Major
>
> I have struggled with this all day and come to the determination that the
> compiler plugin is *not* picking up module-info from dependency jars that put
> it in the multi-release jar location.
> If you reconfigure the dependency to build with module-info at jar root, the
> dependencies get picked up just fine.
> I've prepared a gist based on two projects I help maintain.
> org.jruby.jcodings:jcodings and org.jruby:bytelist.
> [https://gist.github.com/headius/30359f2bbd26852ef545fd54f6fef248]
> As you can see, with the jcodings module-info in the "release 9"
> multi-release jar location, the bytelist module-info is unable to see the
> exported module.
> This makes the multi-release jar feature largely useless for hiding the
> module-info, but putting it in the root of the jar affects any projects or
> libraries that can't understand it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
