You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Michael B?ckling (JIRA)" <ji...@codehaus.org> on 2006/02/15 13:11:19 UTC
[jira] Created: (MJAR-29) Artifact name not correctly calculated
for EAR
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MJAR-29) Artifact name not correctly calculated
for EAR
Posted by "Michael B?ckling (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-29?page=comments#action_58777 ]
Michael Böckling commented on MJAR-29:
--------------------------------------
That is the big question. I do not have enough experience to judge whether or not Wars, Ears, Sars, Rars and whatnot can / should be signed. I can workaround this problem for now by manually specifiying the path to the artifact in the child pom, but htis is of course not optimal.
What I would like to see is a possibility to disable an execution inherited from a parent, something like "<inherited/>" from the childs point of view.
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MJAR-29) Artifact name not correctly calculated
for EAR
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-29?page=comments#action_58742 ]
Brett Porter commented on MJAR-29:
----------------------------------
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?
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org