Failed to create Jar File [...]/jcommander-1.75.jar. #13
Comments
|
Hmm, interesting. Thanks for the report! TL;DR / Temporary WorkaroundTL;DR on this is I'll get it fixed in the next version, in the meantime you can add this above your buildscript {
dependencies {
classpath("com.beust:jcommander") {
version {
strictly("1.77")
}
}
}
}Investigation so farWeirdly, the Jar gradle is caching for jcommander doesn't seem to match the one from However when I unjar the file from the gradle cache (at I am not certain why this is happening (and am a little short on time to investigate at the moment) but upgrading to jcommander 1.77 works around the issue - ideally I'd like to exclude that dependency from the gradle build (it's not needed by the plugin, only when using Jasm from the command-line) but I haven't found a good way to do that without modifying the plugin build itself - at least by forcing the 1.77 version you can do it from your own build script as a temporary workaround. |
|
Yeah I have no idea about what is going on here either, I have literately never seen this before. |
I have the following build script
on Gradle
8.1.1and whenever I run a Gradle command or use Gradle in Idea it can not create~/.gradle/caches/jars-9/7e946c958b720ccfebf883232e04b8b5/jcommander-1.75.jarfor some reason. No other projects are like this and I have deleted the Gradle cache with no change. When checking the filesystem the only file left in7e946c958b720ccfebf883232e04b8b5isjcommander-1.75.jar.lock.lockwhich is a zero byte file.When asked to provide a stack trace Gradle says that
jcommander-1.75.jarhas an invalid manifest with the stack trace at the end of this issue because it's huge.I downloaded the jar from here and the manifest is
which looks valid to my eyes.
I am running Arch with kernel
6.3.5-arch1-1on Java 20.The text was updated successfully, but these errors were encountered: