Artifact name not correctly calculated for EAR
----------------------------------------------
Key: MJAR-29
URL: http://jira.codehaus.org/browse/MJAR-29
Project: Maven 2.x Jar Plugin
Type: Bug
Versions: 2.1
Environment: maven 2.0.2
maven-jar-plugin-2.1-SNAPSHOT
Reporter: Michael Böckling
In a parent POM, I added jar:sign to the plugins section, thus adding it to the
default lifecycle. In a child, I try to build an EAR.
Problem:
- It tries to sign a <artifactId>-<version>.jar instead of
<artifactId>-<version>.ear, thus resulting in an error.
- Should jar:sign really trigger on an EAR artifact at all?
Error message:
[INFO] [jar:sign {execution: jar.sign}]
[INFO] jarsigner: unable to open jar file: C:\Dokumente und Einstellungen\mbo\wo
rkspace\BAL-DruckComponentServer-Ear\target\druck-component-server-ear-0.9-SNAPS
HOT.jar
[INFO] -------------------------------------------------------------------------
---
[ERROR] BUILD ERROR
[INFO] -------------------------------------------------------------------------
---
[INFO] Result of C:\Programme\Java\jdk1.5.0_06\jre\..\bin\jarsigner.exe -keystor
e "C:\Dokumente und Einstellungen\mbo/.keystore" -storepass Giniality -keypass G
iniality -signedjar "C:\Dokumente und Einstellungen\mbo\workspace\BAL-DruckCompo
nentServer-Ear\target\signed\druck-component-server-ear-0.9-SNAPSHOT.jar" "C:\Do
kumente und Einstellungen\mbo\workspace\BAL-DruckComponentServer-Ear\target\druc
k-component-server-ear-0.9-SNAPSHOT.jar" mykey execution is: '1'.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
