Yes, I did.

It should be caused by that signed jars are changed.
But my question is "whether there is a tool to identify which signed jars are 
changed?"

Regards
Simon

Here is stack trace:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:
2.1:analyze (default-cli) on project CoreAppFramework: Execution default-cli of
goal org.apache.maven.plugins:maven-dependency-plugin:2.1:analyze failed: Invali
d signature file digest for Manifest main attributes -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-dependency-plugin:2.1:analyze (default-cli) on pro
ject CoreAppFramework: Execution default-cli of goal org.apache.maven.plugins:ma
ven-dependency-plugin:2.1:analyze failed: Invalid signature file digest for Mani
fest main attributes
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:225)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-c
li of goal org.apache.maven.plugins:maven-dependency-plugin:2.1:analyze failed:
Invalid signature file digest for Manifest main attributes
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:110)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
        ... 19 more
Caused by: java.lang.SecurityException: Invalid signature file digest for Manife
st main attributes
        at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVeri
fier.java:241)
        at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier
.java:196)
        at java.util.jar.JarVerifier.processEntry(JarVerifier.java:266)
        at java.util.jar.JarVerifier.update(JarVerifier.java:220)
        at java.util.jar.JarInputStream.read(JarInputStream.java:193)
        at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:111)
        at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:89)
        at java.util.jar.JarInputStream.getNextEntry(JarInputStream.java:129)
        at java.util.jar.JarInputStream.getNextJarEntry(JarInputStream.java:160)

        at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acc
eptJar(ClassFileVisitorUtils.java:99)
        at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acc
ept(ClassFileVisitorUtils.java:60)
        at org.apache.maven.shared.dependency.analyzer.DefaultClassAnalyzer.anal
yze(DefaultClassAnalyzer.java:46)
        at org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyA
nalyzer.buildArtifactClassMap(DefaultProjectDependencyAnalyzer.java:153)
        at org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyA
nalyzer.analyze(DefaultProjectDependencyAnalyzer.java:72)
        at org.apache.maven.plugin.dependency.AbstractAnalyzeMojo.checkDependenc
ies(AbstractAnalyzeMojo.java:168)
        at org.apache.maven.plugin.dependency.AbstractAnalyzeMojo.execute(Abstra
ctAnalyzeMojo.java:152)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:101)
        ... 20 more

-----Original Message-----
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: 2012年10月17日 12:00
To: Maven Users List
Subject: Re: mvn dependency:analyze failed:Invalid signature file digest for 
Manifest main attributes

>    But you know there are lot of dependency jars there. Is there a 
> tool to identify which signed jar is changed?

Did you try adding -X for debug ouput?

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to