On Thu, 1 Dec 2022 23:21:30 GMT, Magnus Ihse Bursie wrote:
> I have now verified that the interim compiler is indeed used (made it say bad
> words and fail at startup, so there is no doubt about it :)). As to the
> reason why this is so, here is the magic incantation from
> `$(INTERIM_LANGTOOL
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> before were to use `com.sun.tools.javac.Main.compile()`. This me
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> before were to use `com.sun.tools.javac.Main.compile()`. This me
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> before were to use `com.sun.tools.javac.Main.compile()`. This me
On Tue, 22 Nov 2022 20:50:04 GMT, Magnus Ihse Bursie wrote:
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> be
On Tue, 22 Nov 2022 20:50:04 GMT, Magnus Ihse Bursie wrote:
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> be
On Tue, 22 Nov 2022 20:50:04 GMT, Magnus Ihse Bursie wrote:
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> be
In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted out
as a separate buildtool. Due to this, internal classes in jdk.compiler were no
longer available. Therefore, the closest way to calling javac as before were to
use `com.sun.tools.javac.Main.compile()`. This method is
On Tue, 22 Nov 2022 20:50:04 GMT, Magnus Ihse Bursie wrote:
> In JDK-8297041, the javacserver was moved out of the JDK itself, and lifted
> out as a separate buildtool. Due to this, internal classes in jdk.compiler
> were no longer available. Therefore, the closest way to calling javac as
> be
