Support module options via javax.tools.JavaCompiler interface

[stephan-herrmann]

I was alerted by https://mail.openjdk.org/pipermail/compiler-dev/2024-July/027394.html

In particular this statement is of relevance for ecj:

This work removes completely the Plexus compiler API and uses directly the javax.tools.JavaCompiler interface instead.

So, if maven 4 should support compiling with ecj, it should all go through that interface.

Does ecj give access to all relevant options via the javax.tools.JavaCompiler interface?

[stephan-herrmann]

See also #2742

[iloveeclipse]

Does ecj give access to all relevant options via the javax.tools.JavaCompiler interface?

See

eclipse.jdt.core/org.eclipse.jdt.core.compiler.batch/src/org/eclipse/jdt/internal/compiler/tool/EclipseFileManager.java

Line 689 in 8676bca

public boolean handleOption(String current, Iterator<String> remaining) {

for current implementation.

Where one can get list of "relevant options" you mentioned?

[stephan-herrmann]

Does ecj give access to all relevant options via the javax.tools.JavaCompiler interface?

See

eclipse.jdt.core/org.eclipse.jdt.core.compiler.batch/src/org/eclipse/jdt/internal/compiler/tool/EclipseFileManager.java

Line 689 in 8676bca

public boolean handleOption(String current, Iterator<String> remaining) {

for current implementation.

Thanks, this looks quite good, but ...

Where one can get list of "relevant options" you mentioned?

I was thinking of JEP 261. I guess we should support all constants in https://docs.oracle.com/en/java/javase/22/docs/api/java.compiler/javax/tools/StandardLocation.html

And from a quick glance at least PATCH_MODULE_PATH is once more late to the party.