Sean Abraham

I've seen this in multiple build systems actually, both Gradle and Buck. Here's are some stacktrace frames: ``` Caused by: java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at clojure.lang.RT.classForName(RT.java:2154) at clojure.lang.RT.classForName(RT.java:2163)...

This Stackoverflow post further suggests this issue may manifest from how the classloaders are manipulated in IcepickProcess.java: https://stackoverflow.com/questions/22582962/illegalstateexception-zip-file-closed-during-file-write

Just to add to this, this issue is particularly devious in .stg files when the templates are wrapped in `` because with this behavior you have still have to _sometimes_...

You might want to take a look at Clikt as well: https://github.com/ajalt/clikt, https://ajalt.github.io/clikt/whyclikt.html

Am I correct in understanding this is now an issue? I recently updated rules_kotlin to 1.5.0-beta-2 in a pure-JVM project and getting complaints from Bazel about needing to pull `@rules_android`...

Correct me if I'm wrong @cgruber, but I _believe_ this can be remedied in the most recent releases by `load`ing from the correct places (instead of the legacy `kotlin.bzl`) I.e....

Sounds like a good plan to me. My personal solution was to upgrade dependencies but it was a complex web requiring a lot of updates and it would have been...