I'm using maven-assembly-plugin and jar-with-dependencies descriptor to generate an executable jar for my desktop application. But when I try to execute this jar, I have the following exception:
Exception in thread "main" java.lang.SecurityException: no manifiest section for signature file entry javax/activation/DataContentHandlerFactory.class at sun.security.util.SignatureFileVerifier.verifySection( SignatureFileVerifier.java:377) at sun.security.util.SignatureFileVerifier.processImpl( SignatureFileVerifier.java:231) at sun.security.util.SignatureFileVerifier.process( SignatureFileVerifier.java:176) at java.util.jar.JarVerifier.processEntry(JarVerifier.java:233) at java.util.jar.JarVerifier.update(JarVerifier.java:188) at java.util.jar.JarFile.initializeVerifier(JarFile.java:325) at java.util.jar.JarFile.getInputStream(JarFile.java:390) at sun.misc.URLClassPath$JarLoader$1.getInputStream(URLClassPath.java:620) at sun.misc.Resource.cachedInputStream(Resource.java:58) at sun.misc.Resource.getByteBuffer(Resource.java:113) at java.net.URLClassLoader.defineClass(URLClassLoader.java:249) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) And as a matter of fact, as explained in JIRA issues MASSEMBLY-64, RSA and other signature files for activation jar are still in the resulting jar. Is it normal? Is it a known bug? How can I fix this? -- Sébastien Arbogast http://www.sebastien-arbogast.com
