Hi, On Fri, Dec 4, 2015 at 5:12 PM, Alan Bateman <[email protected]> wrote:
> > On 04/12/2015 12:27, Ali Ebrahimi wrote: > > > Just as I said in another thread post: > > 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. > > This will support test modules. > > We've been down this road in the distant past with "requires local" and I > don't think we want to go there again :-) > > We've worked through many testing examples with the current design and > prototype and haven't run into any major issues. The main thing to say is > that TestNG, JUnit and other testing frameworks don't know about modules > yet but we can get existing versions to work okay, it just needs > command-line options that will look complicated at first, esp. when > compiling or injecting test classes into existing modules. I think we > should be confident that the tools and plugins will make this much easier > in time. Just another reason why it's so critical to have tools and eco > system working with us as the module system design (and implementation) > moves forward. > > -Alan > I don't know what was your problem with your "requires local". I think module group concept could made much more easier even jdk modularization task and current non-modular user applications. -- Best Regards, Ali Ebrahimi
