[MJAR-29] Artifact name not correctly calculated for EAR

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.1
• Environment: maven 2.0.2; maven-jar-plugin-2.1-SNAPSHOT
• Assignee: Unassigned
• Reporter: Michael Böckling
• Created: 15/Feb/06 06:11
• Updated: 25/Nov/14 14:30
• Resolved: 25/Nov/14 14:30

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 produces an artifact