Both proguard-base artifacts (com.guardsquare and net.sf.proguard) are in the plugin classpath.
On some machines I have observed, that the proguard goal logs out the version 6.1.1, even though the log states it's using the 7.2.0 jar. This may lead to obfuscation failing:
11:27:58 [INFO] proguard jar: [/home/breno/.m2/repository/com/guardsquare/proguard-base/7.2.0/proguard-base-7.2.0.jar]
11:27:59 [proguard] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/breno/jenkins/workspace/_2877-insight-plugin-licensing_3@tmp/withMavendae6d79d/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/breno/jenkins/workspace/_2877-insight-plugin-licensing_3@tmp/withMavendae6d79d"
11:27:59 [proguard] ProGuard, version 6.1.1
11:27:59 [proguard] Exception in thread "main" java.lang.NoSuchMethodError: 'void proguard.io.ClassReader.<init>(boolean, boolean, boolean, proguard.classfile.util.WarningPrinter, proguard.classfile.visitor.ClassVisitor)'
11:27:59 [proguard] at proguard.InputReader.execute(InputReader.java:95)
11:27:59 [proguard] at proguard.ProGuard.readInput(ProGuard.java:266)
11:27:59 [proguard] at proguard.ProGuard.execute(ProGuard.java:97)
11:27:59 [proguard] at proguard.ProGuard.main(ProGuard.java:591)
I haven't found any dependency declaration on net.sf.proguard:proguard-base in the plugin code, and am really confused about where this is coming from.
I have reproduced the above with different JDK versions (17, 11) and with maven 3.6.3.
I have the following plugin configuration
Running the proguard maven goal with the
-X
option yields the following dependency resolution:Which leads to
Both proguard-base artifacts (com.guardsquare and net.sf.proguard) are in the plugin classpath.
On some machines I have observed, that the proguard goal logs out the version 6.1.1, even though the log states it's using the 7.2.0 jar. This may lead to obfuscation failing:
I haven't found any dependency declaration on
net.sf.proguard:proguard-base
in the plugin code, and am really confused about where this is coming from.I have reproduced the above with different JDK versions (17, 11) and with maven 3.6.3.
This issue could be related with https://github.com/wvengen/proguard-maven-plugin/issues/235 and https://github.com/wvengen/proguard-maven-plugin/issues/141.