Róbert Papp

Workaround: ```gradle // TODO delete when https://github.com/bumptech/glide/issues/5601 is resolved. tasks .named { it == "compileDebugAndroidTestKotlin" } .configureEach { org.jetbrains.kotlin.gradle.tasks.KotlinCompile task -> task.compilerOptions.freeCompilerArgs.add("-Xwarning-level=EXPOSED_PACKAGE_PRIVATE_TYPE_FROM_INTERNAL_WARNING:disabled") } ``` Change the task name to whatever...

Asked for help here: https://youtrack.jetbrains.com/issue/KTLC-271/No-exposed-visibility-error-on-internal-class-inheriting-from-package-private-Java-class#focus=Comments-27-12638916.0-0

I wonder if this is an option as a "solution": https://livefront.com/writing/suppressing-annoying-kotlin-compiler-warnings/ Glide already publishes a KSP, so it might be able to hook into this.

@jaredsburrows I'm not sure what you mean by root. The workaround needs to be applied on the tasks which fail. Check the error message carefully. It'll be most likely on...

Any idea when we go to stable from the alphas? It would be nice to go stable, and if need be release a 3.x major again if there's anything big,...

Are we sure NONE is the right sensitivity? If the files are relocated, wouldn't we need to invalidate the inputs and re-run the task? Or is that not what it...

Should we report this to Gradle? `org.gradle.reporting.CodePanelRenderer` doesn't look like an internal name to me, yet they clearly treat it as such ([breaking change in minor is here](https://github.com/gradle/gradle/commit/1b56084b4717d37625394124cc2a3e5806c5129b)).

Makes sense, I'll raise an issue for them to clarify internalness here.

As a quick fix, `if(GradleVersion` + reflection? So we can use it on both Gradle 9.0 and 9.1? Edit: ah you opened https://github.com/cashapp/paparazzi/pull/2112, makes sense.

* https://github.com/gradle/gradle/issues/35086