the JarSignMojo signs the original jar, and then does project.getArtifact().setFile(signedJar) which basically tells all later plugins that this is the output of this project. That's probably why surefire is usign the signed jar. If you want to avoid this, assign a classifier to the signed jar.
Tom On 1/10/07, Christian Goetze <[EMAIL PROTECTED]> wrote:
diroussel wrote: >The question is, why is surefire not using the un-signed jar. I have two >jars: >target\MyJar.jar >target\signed\MyJar.jar > >so why is surefire choosing the second one, not the normal one in the normal >place. > >Any ideas? > > > No ideas here, sorry.... Just wanted to add my opinion that the jar signing should really be in the assembly plugin. It is not very useful to have it in the jar plugin, since all the third party jars which get pulled in via transitive dependencies won't get signed. Currently, I do the jar signing as a post-processing step outside of maven, for that reason. A pity, if you ask me... -- cg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
