On Tue, Dec 8, 2015 at 2:26 PM, Neil Bartlett <njbartl...@gmail.com> wrote:
> I suspect a more common approach will be to generate module-info.class > directly, skipping the Java source file, since module-info.class is > extensible whereas module-info.java is not. > Neil, I think you are right. That's a very good point. Thank you. I forgot not everything planned is expressible as Java source. Since module-info.class can contain custom attributes, tools wishing to append custom attributes have to write them straight into the class file. There is no intermediate representation. Well, I hope tools (javap?) will be readily available to dump that file into some human-readable format so it's easy to investigate, debug, and patch. Cheers, Paul
