Module metadata doesn't really need to be .class

Paul Benedict pbenedict at
Thu Sep 24 01:29:15 UTC 2015

So I was happy to see the .jmod be in zip format. That allows universal
tooling to access the contents.

I am unhappy to see the module info to be a class file. I can't agree with
the justification. I believe David Lloyd brought up a similar issue. There
is nothing about the module data requires language support. It's just
metadata. This easily could have been put in a MANIFEST.MF or an XML
descriptor. What is the benefit for having it be binary ... as a Java class
file? It makes no sense and would like this to be reconsidered.


More information about the jpms-spec-observers mailing list