modulepath and classpath mixture

Alex Buckley alex.buckley at oracle.com
Tue Feb 23 00:30:16 UTC 2016


Hi Robert,

On 2/22/2016 12:44 PM, Robert Scholte wrote:
> 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.

Sounds good.

> 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.

To clarify: you are NOT putting module-info.java in src/test/java.

> 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.

Your first approach sounds preferable. Can you copy-paste a minimized 
invocation of javac that works, and that doesn't work?

Alex


More information about the jigsaw-dev mailing list