maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Oliver Nutter (JIRA)" <>
Subject [jira] [Commented] (MCOMPILER-361) module-info in multi-release jar is not picked up by compile
Date Thu, 06 Sep 2018 06:38:00 GMT


Charles Oliver Nutter commented on MCOMPILER-361:

Ok, so the missing bit may simply be that when producing a multi-release jar, you must also
set a property in the MANIFEST.MF file.

See discussion here: []

This does appear to get past the compile phase in the dependent project, but then the javadoc
plugin fails to recognize the "mrjar" module.

So the remaining issue here is whether the compiler or jar plugins should be "smartened up"
so that using "multiReleaseOutput" actually does *all* the steps necessary to produce an actually-useful
multi-release jar.

> module-info in multi-release jar is not picked up by compile
> ------------------------------------------------------------
>                 Key: MCOMPILER-361
>                 URL:
>             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
> 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.
> []
> 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

This message was sent by Atlassian JIRA

View raw message