signing in multi-module project fails on windows

Details

Type: Bug
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 1.2
Fix Version/s: None
Labels:
None
Environment:
Windows XP, android sdk

Number of attachments :
1

Description

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 1"

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:

[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]

Attaching pom file which I am using.
Please help?

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

pom.xml

28/Feb/11 8:42 AM

3 kB

Anna Gadomska

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Dennis Lundberg added a comment - 28/Feb/11 1:48 PM

What is the error message you get from jarsigner if you run it directly from the command line?

cmd.exe /X /C "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore "C:\tmp\debug.keystore" -storepass '*****' -keypass '*****' xxx.jar '*****'debugkey"

Show

Dennis Lundberg added a comment - 28/Feb/11 1:48 PM What is the error message you get from jarsigner if you run it directly from the command line? cmd.exe /X /C "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore "C:\tmp\debug.keystore" -storepass '*****' -keypass '*****' xxx.jar '*****'debugkey"

Hide

Permalink

Anna Gadomska added a comment - 28/Feb/11 1:54 PM

Dennis, it works fine when I call it from command line, separately for every module

Show

Anna Gadomska added a comment - 28/Feb/11 1:54 PM Dennis, it works fine when I call it from command line, separately for every module

Hide

Permalink

Dennis Lundberg added a comment - 28/Feb/11 2:06 PM

OK, what about from the parent?

Show

Dennis Lundberg added a comment - 28/Feb/11 2:06 PM OK, what about from the parent?

Hide

Permalink

Dennis Lundberg added a comment - 28/Feb/11 2:09 PM

Also you can try to run mvn with the -X command line option to run in debug mode. Hopefully you'll get a helpful error message or stack trace at the end.

Show

Dennis Lundberg added a comment - 28/Feb/11 2:09 PM Also you can try to run mvn with the -X command line option to run in debug mode. Hopefully you'll get a helpful error message or stack trace at the end.

Hide

Permalink

Ton van Bart added a comment - 18/Mar/11 10:13 AM - edited

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] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[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 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
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
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 mykey"'
 - exitcode 1
        at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.processArchive(AbstractJarsignerMojo.java:495)
        at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.processArtifact(AbstractJarsignerMojo.java:372)
        at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.execute(AbstractJarsignerMojo.java:197)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        ... 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] ------------------------------------------------------------------------
C:\workspaces_STS\rct-mavenized\test\testapplet>

This particular project is for test, but it is a proof-of-concept that will be merged into a production project.

Show

Ton van Bart added a comment - 18/Mar/11 10:13 AM - edited 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] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [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 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 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) 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 mykey" ' - exitcode 1 at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.processArchive(AbstractJarsignerMojo.java:495) at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.processArtifact(AbstractJarsignerMojo.java:372) at org.apache.maven.plugins.jarsigner.AbstractJarsignerMojo.execute(AbstractJarsignerMojo.java:197) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 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] ------------------------------------------------------------------------ C:\workspaces_STS\rct-mavenized\test\testapplet> This particular project is for test, but it is a proof-of-concept that will be merged into a production project.

Hide

Permalink

Juan Pablo added a comment - 29/Apr/11 9:59 AM

Hello all,

I've this problem too and it seems to be (in my case), a problem when defining plugin configuration from parent's. POM.
I have a 3 level multimodule project with many modules inside and i choosed to configure jarsigner in topmost one (just to avoid duplicate configurations), and when using relative paths (or even $

{basedir}

), it always tries to load the keystore from withing "current" module path:

"H:\opt\java\jdk1.6.0_24_x86\jre\..\bin\jarsigner.exe -keystore H:\projects\��\java\trunk\client\launcher\workspace\keystore\signing-jar.keystore -storepass '****' -keypass '***' H:\projects\java\trunk\client\launcher\target\client-launcher-04.08.0000.jar '****'"'
: java.lang.RuntimeException: keystore load: H:\projects\java\trunk\client\launcher\workspace\keystore\signing-jar.keystore (The system cannot find the path specified)

(seen when running maven with -X option (thanks, btw )

Hope this helps

Show

Juan Pablo added a comment - 29/Apr/11 9:59 AM Hello all, I've this problem too and it seems to be (in my case), a problem when defining plugin configuration from parent's. POM. I have a 3 level multimodule project with many modules inside and i choosed to configure jarsigner in topmost one (just to avoid duplicate configurations), and when using relative paths (or even $ {basedir} ), it always tries to load the keystore from withing "current" module path: "H:\opt\java\jdk1.6.0_24_x86\jre\..\bin\jarsigner.exe -keystore H:\projects\��\java\trunk\client\launcher\workspace\keystore\signing-jar.keystore -storepass '**** ' -keypass ' *** ' H:\projects\java\trunk\client\launcher\target\client-launcher-04.08.0000.jar ' ****'"' : java.lang.RuntimeException: keystore load: H:\projects\java\trunk\client\launcher\workspace\keystore\signing-jar.keystore (The system cannot find the path specified) (seen when running maven with -X option (thanks, btw ) Hope this helps jp

Hide

Permalink

Paul Vonnahme added a comment - 31/Jan/12 4:05 PM

This appears to still be an issue. I tested it on Windows 2003 and maven 3.0.4 (the latest at this time). I found this info: http://stackoverflow.com/questions/7421710/android-maven-jarsigner-jarsigner-attempt-to-rename-x-but-failed

Which links to this blog with a workaround (workaround is to use maven-jar-plugin): http://www.jameselsey.co.uk/blogs/techblog/automating-android-application-signing-and-zipaligning-with-maven/

If I try to sign & verify via two different executions within the jarsigner plugin configuration, I get the error. However, if I sign with an execution step in the maven-jar-plugin and then verify with an execution step in the maven-jarsigner-plugin, it works.

Show

Paul Vonnahme added a comment - 31/Jan/12 4:05 PM This appears to still be an issue. I tested it on Windows 2003 and maven 3.0.4 (the latest at this time). I found this info: http://stackoverflow.com/questions/7421710/android-maven-jarsigner-jarsigner-attempt-to-rename-x-but-failed Which links to this blog with a workaround (workaround is to use maven-jar-plugin): http://www.jameselsey.co.uk/blogs/techblog/automating-android-application-signing-and-zipaligning-with-maven/ If I try to sign & verify via two different executions within the jarsigner plugin configuration, I get the error. However, if I sign with an execution step in the maven-jar-plugin and then verify with an execution step in the maven-jarsigner-plugin, it works.

People

Assignee:

Unassigned

Reporter:

Anna Gadomska

Vote (3)

Watch (5)

Dates

Created:

28/Feb/11 8:42 AM

Updated:

31/Jan/12 4:05 PM