Hi,

first of all I'd like to say that I'm very pleased with the new -mp options, these matches better with the way Apache Maven would like to work with jars and class-folders.

Here's my use case: I noticed that if I add a module-info to src/main/java and put all compile-scoped dependencies to the module path, all compiles fines. I assume that developers are less interested in adding a module-info.java file to src/test/java, so that's what I'm doing right now too. Now it seems that I *must* add compile + test scoped to the *classpath* to be able to compile the test classes. My first approach was to leave the compile-scoped dependencies on the modulepath and all test-scoped dependencies on the classpath, so the modules keeps their inner related structure, but it seems that the classpath classes cannot access the modulepath classes.

I'm looking for the confirmation that putting all dependencies on the classpath is indeed the right approach in this case.

thanks,
Robert

Reply via email to