> AIUI no, it’s a problem when loading gradle’s JVM, but Dawid might have a
> better idea?
No better ideas, sorry. This 'gradle.properties' file is a convenience
template - it is there for folks to modify and tweak. Occasionally
we'll have to add things there (or modify things there) and they
I stopped the gradle daemon (./gradlew --stop) and deleted the
gradle.properties. I'm still getting the same error though. My new
gradle.properties has the following:
org.gradle.jvmargs=-Xmx3g \
--add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED \
--add-exports
AIUI no, it’s a problem when loading gradle’s JVM, but Dawid might have a
better idea?
> On 24 Jan 2022, at 13:50, Mike Drob wrote:
>
> Is there a way to check for these missing module exports early and fail with
> a more informative message?
>
> On Mon, Jan 24, 2022 at 7:42 AM Alan Woodward
Is there a way to check for these missing module exports early and fail
with a more informative message?
On Mon, Jan 24, 2022 at 7:42 AM Alan Woodward wrote:
> Hey Joel,
>
> The fix for this is to delete the gradle.properties file in the root
> directory and stop any daemons before running
Hey Joel,
The fix for this is to delete the gradle.properties file in the root directory
and stop any daemons before 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
