[jira] [Created] (MCOMPILER-361) module-info in multi-release jar is not picked up by compile

["Charles Oliver Nutter (JIRA)" <ji...@apache.org>]

Charles Oliver Nutter created MCOMPILER-361:
-----------------------------------------------

             Summary: 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


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)