Option to keep the source of generated module-info.class?

[laeubi]

I'm currently try to migrate some hand crafted modules info to bnd. It would be useful to get the "source" of that generated file so I don't need to inspect the class file for an difference, e.g. moditect-maven-plugin uses a <moduleSource> that looks like this:

open module org.eclipse.osgi {
	requires java.xml;
	requires static jdk.unsupported;

	exports org.eclipse.equinox.log;
	...

	provides org.osgi.framework.launch.FrameworkFactory with org.eclipse.osgi.launch.EquinoxFactory;
	provides org.osgi.framework.connect.ConnectFrameworkFactory with org.eclipse.osgi.launch.EquinoxFactory;

	uses org.osgi.framework.connect.FrameworkUtilHelper;
}

it would be good if bnd could provide similar output and dump it into a file if configured.

[bjhargrave]

We don't make the source file. We just generate the class file. So I don't see that we will add source generation for module-info.

[laeubi]

We don't make the source file.

Thanks for the feedback, yes currently no source is created that's what this issue is about :-)

We just generate the class file.

Nerveless BND has a internal representation of the JPMS that is then transformed into a java class-file, so it should be possible to write that out into an equivalent java-source representation.