usage of com.sun.tools.javac.Main

[Jochen Theodorou]

On 26.07.2016 09:11, Alan Bateman wrote:
> On 26/07/2016 07:58, Jochen Theodorou wrote:
>
>> Hi all,
>>
>> when I tried the Groovy build jigsaw about 2 months ago the usage of
>> com.sun.tools.javac.Main required me to make the module it was defined
>> in to be accessible for the unnamed module. In the latest version I
>> tried this was not required anymore, which was I think JDK9 b128.
>>
>> Did I use a JDK in which this was not enforced or is there a change
>> for com.sun.tools.javac.Main?
>>
>> PS: I know I should not use this class and I was about to change this,
>> when I noticed that I am missing the error messages about this.
> The javac man page documents the entry point com.sun.tools.javac.Main
> (the "old interface") and com.sun.tools.javac continues to be exported.
> I don't recall a time when it wasn't exported. Jon or Jan might know
> more about this. In any case, maybe it is time to move to javax.tools?

Around April 10 this year I had to use 
-XaddExports:jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED to get 
access using the jigsaw build, which means there was a module 
jdk.compiler, that did not export this class.

bye Jochen