Invalid Signature File Error While Executing .jar
When running a .jar file containing a dependency on an external library (e.g., bouncy castle), users may encounter the following error:
java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
This error often indicates an issue with the jar's digital signature.
Solution for Maven-Shade-Plugin Users
For users creating shaded uber-jars using the maven-shade-plugin, the solution lies in excluding the manifest signature files from the shading process. Add the following lines to the plugin's configuration:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-shade-plugin</artifactId> <configuration> <filters> <filter> <artifact>*:*</artifact> <excludes> <exclude>META-INF/*.SF</exclude> <exclude>META-INF/*.DSA</exclude> <exclude>META-INF/*.RSA</exclude> </excludes> </filter> </filters> <!-- Additional configuration. --> </configuration> </plugin>
By excluding these files, the shaded uber-jar will not contain the conflicting signature information, resolving the "Invalid signature file" error.
The above is the detailed content of How to Fix 'Invalid signature file digest for Manifest main attributes' Error in Shaded JAR Files?. For more information, please follow other related articles on the PHP Chinese website!