On 11/07/2017 02:25 PM, Stephan Herrmann wrote:
Thanks a lot, Jon,
This is very helpful.
As you mention legacy mode as "no modules being compiled", this mode
is still tied to the -source, -target, and --release options, right?
Strongly related, yes, but not directly tied together.
Set asid
Thanks a lot, Jon,
This is very helpful.
As you mention legacy mode as "no modules being compiled", this mode
is still tied to the -source, -target, and --release options, right?
IOW, the fact that the command line without module-info.java succeeds
is not owed to using a different compilation m
On 11/07/2017 12:56 PM, Stephan Herrmann wrote:
On 07.11.2017 21:43, Alan Bateman wrote:
On 07/11/2017 18:56, Stephan Herrmann wrote:
I recently noticed that compilers start to ignore -classpath as soon
as module-info (.java or .class) is found during the compile.
(Incidentally, javac and Ecl
On 07.11.2017 21:43, Alan Bateman wrote:
On 07/11/2017 18:56, Stephan Herrmann wrote:
I recently noticed that compilers start to ignore -classpath as soon
as module-info (.java or .class) is found during the compile.
(Incidentally, javac and Eclipse compiler agree in this).
Using a trivial test
On 07/11/2017 18:56, Stephan Herrmann wrote:
I recently noticed that compilers start to ignore -classpath as soon
as module-info (.java or .class) is found during the compile.
(Incidentally, javac and Eclipse compiler agree in this).
Using a trivial test class this works:
$ javac -classpath juni
I recently noticed that compilers start to ignore -classpath as soon
as module-info (.java or .class) is found during the compile.
(Incidentally, javac and Eclipse compiler agree in this).
Using a trivial test class this works:
$ javac -classpath junit4.jar -d bin/ src/pkg/TestJUnit4.java
This d
