Thomas Broyer
Thomas Broyer
You could probably rule out the "shared non-thread safe instance" option by configuring maven-compiler-plugin to fork (you'll probably have to copy the `--add-opens`/`--add-exports` to ``, prefixing them with `-J`; see...
Afaict it determines what can be parsed but not how it'll be formatted.
Fwiw, `%s` is only safe if the corresponding argument is not `Formattable`.
Fwiw, Gradle has a JavaVersion enum that's meant to be comparable, even though it also has an isCompatibleWith method (that just delegates to compare to). In Kotlin and Groovy it...
You shouldn't need the `gwt-codeserver` dependency, as the classes are already included into `gwt-dev`, but those also must not be declared with `provided`. Have you read https://tbroyer.github.io/gwt-maven-plugin/codeserver.html ? Have you...
This is #110. It's specific to Windows.
This is by-design (https://github.com/google/error-prone/commit/04fe8357e885ff17990b0558379bbe158397b23c) Shouldn't this be fixed in Bazel's rules_jvm_external to properly handle relocations?
Guava needs to be updated to avoid deprecation warnings with JDK 25: ``` WARNING: A terminally deprecated method in sun.misc.Unsafe has been called WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper...
IIUC, the way Gradle will snapshot that is dependent on the classloaders. Could there be a difference between the machines that could influence that? Anyway, I'm not sure there's something...
Ideally the forbidden APIs task would use Gradle's Worker API so it can itself use a toolchain (and default to using the default toolchain). That implies no longer supporting antiquated...