module-info.java just causes problems

[Gunnar Morling]

This also ties in with the question of overriding required modules
dependencies I raised recently [1].

Assuming a developer needs to change the module requirements of one of the
modules they use, this means - as far as I understand the current design -
they need to get the source of the module's module-info.java, adapt it as
needed and re-compile it.

Given how often I find myself re-working transitive dependency sets of
Maven artifacts I depend on (e.g. to exclude things not needed for my case,
or to only have a single source of the javax.transaction packages), I hope
there'll be a way for controlling these things which doesn't include
reworking module-info.java as described above.

--Gunnar

[1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007617.html


2016-05-04 20:33 GMT+02:00 David M. Lloyd <david.lloyd at redhat.com>:

> Tools like Maven and JUnit are yet still having a difficult time coping
> with the oddball module-info.java file.  Can we just drop this thing and
> let the layer provide metadata for the module?  This way of defining module
> metadata is clearly causing trouble.  Reference: all previous arguments
> from non-Oracle people over the last 5 years or so.
>
> So far none of our software actually functions with Jigsaw, and the
> prospect is not improving.  In the meantime the EG is alternately
> completely dead or in a state of
> we'll-register-your-issue-but-cannot-help-resolve-them mode.  I'm highly
> concerned.
> --
> - DML
>