[ http://jira.codehaus.org/browse/MJAR-32?page=comments#action_59324 ]
Pawel Pastula commented on MJAR-32:
-----------------------------------
There is also one thing I forgot in my last comment.
To enable in-place jar signing, the field signedjar must not be @requiered.
Right now tests are working fine but there is no way to do it in practise.
I had removed @requiered attribute and have been struggling with pom.xml to
make it work.
The "default-value" makes it difficult to set null value. I don't know maven2
well but if there is no way to set this plugin's attribute to null then I think
signedjar should be String not java.io.File.
I tried:
<signedjar/> and thoutht it could set signedjar to null - but the default value
is set
I also tried:
<signedjar implementation="java.io.File">null</signedjar> but creates
File("null") :-)
How can one set this field to null to enable in-place jar signing ?
> [JarSignMojo] Verification of a signed jar fails
> ------------------------------------------------
>
> Key: MJAR-32
> URL: http://jira.codehaus.org/browse/MJAR-32
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Environment: Linux Slackware 10.1, JDK 1.4.2_02
> Reporter: Pawel Pastula
> Priority: Blocker
> Attachments: MJAR-32.diff
>
>
> When verification is executed there is no way the verification can succeed
> since if uses unsigned jar file instead of signedjar file:
> verify.setJarPath( getJarFile() ); in JarSignMojo.java:182.
--
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]
