roscopeco
commented
1 year ago Hmm, interesting. Thanks for the report!
TL;DR / Temporary Workaround
TL;DR on this is I'll get it fixed in the next version, in the meantime you can add this above your plugins block as a workaround:
buildscript {
dependencies {
classpath("com.beust:jcommander") {
version {
strictly("1.77")
}
}
}
}Investigation so far
Weirdly, the Jar gradle is caching for jcommander doesn't seem to match the one from repo1.maven. When I grabbed the jar you linked above (which is also linked from the official Maven repo listing), I did indeed see the valid (if minimal) manifest you showed above.
However when I unjar the file from the gradle cache (at /Users/<MYUSER>/.gradle/caches/modules-2/files-2.1/com.beust/jcommander/1.75) I see the following manifest, which is obviously incorrect (and in fact the extraneous manifest entry begins on line 18, as pointed to by the error trace):
Bundle-Description: A Java library to parse command line options
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0
Export-Package: com.beust.jcommander.converters;version="1.75",com.beu
st.jcommander.defaultprovider;version="1.75",com.beust.jcommander;ver
sion="1.75",com.beust.jcommander.internal;version="1.75",com.beust.jc
ommander.validators;version="1.75"
Build-Date: 2019-03-16
Bundle-SymbolicName: jcommander
Bundle-Version: 1.75
Bundle-Name: com.beust.jcommander
Bundle-ManifestVersion: 2
Bnd-LastModified: 1552771161835
Created-By: 1.8.0_191 (Oracle Corporation)
Tool: Bnd-3.5.0.201709291849
Manifest-Version: 1.0
Bundle-Description: A Java library to parse command line options
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0
Export-Package: com.beust.jcommander.converters;version="1.75",com.beu
st.jcommander.defaultprovider;version="1.75",com.beust.jcommander;ver
sion="1.75",com.beust.jcommander.internal;version="1.75",com.beust.jc
ommander.validators;version="1.75"
Build-Date: 2019-03-16
Bundle-SymbolicName: jcommander
Bundle-Version: 1.75
Bundle-Name: com.beust.jcommander
Bundle-ManifestVersion: 2
Bnd-LastModified: 1552771171001
Created-By: 1.8.0_191 (Oracle Corporation)
Tool: Bnd-3.5.0.201709291849I 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.
gudenau
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.