modulepath and classpath mixture
Alan Bateman
Alan.Bateman at oracle.com
Wed Mar 23 07:14:24 UTC 2016
On 22/03/2016 21:23, Robert Scholte wrote:
>> maven-builder-support/src/test/java/org/apache/maven/building/DefaultProblemTest.java:[1,1]
>> package exists in another module: maven.builder.support
>
> Just wondering, is this the expected behavior?
>
> DefaultProblemTest is on the *classpath* and I wouldn't expect that these
> entries would have any effect on the modulepath entries. I would
> expect that the packages between modules are checked, and that all
> these packages are exposed to the classpath; no extra check if
> classpath packages are in conflict with module packages.
> The message says ' in *another* module', but this directory is not a
> module, which makes it extra confusing.
It looks like it is trying to compile
org/apache/maven/building/DefaultProblemTest.java on the class path
(unnamed module) but package org.apache.maven.building is in module
maven.builder.support on the module path.
I think this is back to needing the module name as this can only work if
you compile the test as if it is part of the module, meaning
-Xmodule:maven.builder.support here.
-Alan
More information about the jigsaw-dev
mailing list