maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ton van Bart (JIRA)" <>
Subject [jira] Commented: (MJARSIGNER-13) signing in multi-module project fails on windows
Date Fri, 18 Mar 2011 15:13:23 GMT


Ton van Bart commented on MJARSIGNER-13:

I have the same problem with a build developed on OSX which fails on Windows (XP - my employer
hasn't upgraded yet).
Running "mvn install -X" ends with the following messages and stack trace:
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign' -->
[DEBUG]   (f) alias = mykey
[DEBUG]   (f) arguments = []
[DEBUG]   (f) keystore = src/main/signing/testkeys
[DEBUG]   (f) processAttachedArtifacts = true
[DEBUG]   (f) processMainArtifact = true
[DEBUG]   (f) project = MavenProject: org.vanbart:testapplet:0.0.1-SNAPSHOT @ C:\workspaces_STS\rct-mavenized\test\testapplet\pom.xml
[DEBUG]   (f) removeExistingSignatures = false
[DEBUG]   (f) skip = false
[DEBUG]   (f) storepass = test123
[DEBUG]   (f) verbose = false
[DEBUG] -- end configuration --
[INFO] [jarsigner:sign {execution: sign}]
[DEBUG] Processing C:\workspaces_STS\rct-mavenized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar
[DEBUG] 'cmd.exe /X /C ""C:\Program Files\Java\jdk1.6.0_17\jre\..\bin\jarsigner.exe" -keystore
src/main/signing/testkeys -storepass '*****' C:\workspa
ces_STS\rct-mavenized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar mykey"'
[DEBUG] jarsigner: attempt to rename C:\workspaces_STS\rct-mavenized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar
to C:\workspaces_STS\rct-mav
enized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar.orig failed
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Failed executing 'cmd.exe /X /C ""C:\Program Files\Java\jdk1.6.0_17\jre\..\bin\jarsigner.exe"
-keystore src/main/signing/testkeys -storepass '*
****' C:\workspaces_STS\rct-mavenized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar
mykey"' - exitcode 1
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed executing 'cmd.exe /X /C ""C:\Program
-keystore src/main/signing/testkeys -storepass '*****' C:\workspaces_STS\rct-mavenized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar
mykey"' -
exitcode 1
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
        at org.apache.maven.DefaultMaven.doExecute(
        at org.apache.maven.DefaultMaven.execute(
        at org.apache.maven.cli.MavenCli.main(
        at org.apache.maven.cli.compat.CompatibleMain.main(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.codehaus.classworlds.Launcher.launchEnhanced(
        at org.codehaus.classworlds.Launcher.launch(
        at org.codehaus.classworlds.Launcher.mainWithExitCode(
        at org.codehaus.classworlds.Launcher.main(
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed executing 'cmd.exe /X /C
""C:\Program Files\Java\jdk1.6.0_17\jre\..\bin\jarsigner.ex
e" -keystore src/main/signing/testkeys -storepass '*****' C:\workspaces_STS\rct-mavenized\test\testapplet\target\testapplet-0.0.1-SNAPSHOT.jar
 - exitcode 1
        at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.processArchive(
        at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.processArtifact(
        at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.execute(
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
        ... 17 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Fri Mar 18 16:05:56 CET 2011
[INFO] Final Memory: 21M/38M
[INFO] ------------------------------------------------------------------------
This particular project is for test, but it is a proof-of-concept that will be merged into
a production project.

> signing in multi-module project fails on windows
> ------------------------------------------------
>                 Key: MJARSIGNER-13
>                 URL:
>             Project: Maven 2.x Jar Signer Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Windows XP, android sdk 
>            Reporter: Anna Gadomska
>         Attachments: pom.xml
> I got multi-module (6 modules) android project with .pom file and "sign" profile defined.
When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution (mv <goal>
-rf) it signs another 3 modules and fails again. The reason for failing is: [INFO] jarsigner:
attempt to rename xxx.jar to xxx.jar.orig failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns "error code
> However, I tried the same .pom - everything works perfectly in Linux (Ubuntu). 
> I was afraid that it might be the issue with spaces, so I hardcoded the paths - the error
I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign
(signing) on project MyProject: Failed executing 'cmd.exe /X /C "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe
-verbose -keystore "C:\tmp\debug.keystore" -storepass '*****' -keypass '*****' xxx.jar '*****'debugkey"'
- exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message