> the reason you are running into issues is
> because the second javac command is essentially compiling a module with
> references to types on the class path.
Shouldn't this be supported, though?
I.e. is the observed behavior a bug and the contents from the given
classpath should actually be avai
It’s also possible to do this:
javac --source-path=src/main/java9 --source-path=src/main/java -implicit:none
-d target/classes-java9 --release 9 $(find src/main/java9 -name "*.java”)
but that approach is fragile (it assumes the implicitly referenced source can
be processed for release 8 and 9).
On 10/02/2017 23:06, Gunnar Morling wrote:
:
If I don't have a module descriptor things work fine:
javac --source-path=src/main/java -d target/classes --release 8
$(find src/main/java -name "*.java")
javac --source-path=src/main/java9 -cp target/classes -d
target/classes-java9 --rele
