You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Juan Pablo (JIRA)" <ji...@codehaus.org> on 2011/04/29 17:01:22 UTC
[jira] Commented: (MJARSIGNER-13) signing in multi-module project
fails on windows
[ http://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265235#action_265235 ]
Juan Pablo commented on MJARSIGNER-13:
--------------------------------------
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
> signing in multi-module project fails on windows
> ------------------------------------------------
>
> Key: MJARSIGNER-13
> URL: http://jira.codehaus.org/browse/MJARSIGNER-13
> 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 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:
> {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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira