Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:maven 2.0.2
maven-jar-plugin-2.1-SNAPSHOT
-
Number of attachments :
Description
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'.
Issue Links
- relates to
-
MJAR-27
jar:sign doesn't check if project prouces an artifact
-
This is a bit tricky. You are telling Maven to run that goal every time. Presumably to save space by including a portion of that in each subproject (the configuration could still be shared via pluginManagement).
We could make jar:sign a no-op if packaging != jar - but is that correct? are there other packagings that still produce a jar and should be signable?