orts that
>> work around this problem in the formatter.
>>
>> - A
>>
>> On 24 Jan 2022, at 13:33, Joel Bernstein wrote:
>>
>> Hi.
>>
>> I'm getting the following gradlew check failure with Java 17 on the lucene
>>
will regenerate the gradle.properties file with some module exports
>> that work around this problem in the formatter.
>>
>> - A
>>
>> On 24 Jan 2022, at 13:33, Joel Bernstein wrote:
>>
>> Hi.
>>
>> I'm getting the
th some module exports that work
> around this problem in the formatter.
>
> - A
>
>> On 24 Jan 2022, at 13:33, Joel Bernstein > <mailto:joels...@gmail.com>> wrote:
>>
>> Hi.
>>
>> I'm getting the following gradlew check fail
fore running gradle check again. The
> build will regenerate the gradle.properties file with some module exports
> that work around this problem in the formatter.
>
> - A
>
> On 24 Jan 2022, at 13:33, Joel Bernstein wrote:
>
> Hi.
>
> I'm getting the following g
022, at 13:33, Joel Bernstein <mailto:joels...@gmail.com>> wrote:
>
> Hi.
>
> I'm getting the following gradlew check failure with Java 17 on the lucene
> main branch:
>
> Caused by: java.lang.IllegalAccessError: class
> com.google.googlejavaformat.java
Hi.
I'm getting the following gradlew check failure with Java 17 on the lucene
main branch:
Caused by: java.lang.IllegalAccessError: class
com.google.googlejavaformat.java.JavaInput (in unnamed module @0x3d6a6107)
cannot access class com.sun.tools.javac.parser.Tokens$TokenKind (in m