is ClassLoader.loadClass() supposed to work on module-info classes?
ali.ebrahimi1781 at gmail.com
Fri Dec 4 10:33:29 UTC 2015
On Fri, Dec 4, 2015 at 4:33 AM, Alex Buckley <alex.buckley at oracle.com>
> On 12/3/2015 4:47 AM, David M. Lloyd wrote:
> If you're splitting or merging modules -- especially someone else's! --
> then you need to let the compiler check that the newly factored modules are
> well-formed: they export packages that they actually contain, and they
> don't read anything that would lead to a split package. (The constraints in
> j.l.m.Configuration::resolve, basically.)
> Similarly, if you're changing a module to require a module by Vendor X
> rather than Vendor Y, then you'll want the compiler to check that your
> module isn't led by Vendor X's module to read anything that would lead to a
> split package.
> Better to modify module-info.java and recompile it and catch these issues
> up front, than modify MANIFEST.MF and run the main module and hope the
> tests catch them.
If we have module group concept and modules belong to same module group
loaded by same classloader then we can support splited packages. This way
each module group maps to each classloader.
More information about the jigsaw-dev