[
https://jira.codehaus.org/browse/MJARSIGNER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338499#comment-338499
]
Tony Chemit edited comment on MJARSIGNER-30 at 1/12/14 6:09 PM:
----------------------------------------------------------------
With jdk <1.8, when can not verify a jar then exit code is 1 (this is normal);
while with jdk 1.8, result code is 0.
IMHO, this is a bug from jdk 1.8: when a command fails, you can't have a result
code to 0.
We need to open/track this *regression*.
was (Author: tchemit):
With jdk <1.8, when can not verify a jar then exit code is 1 (this is
normal); while with jdk 1.8, result code is 0.
IMHO, this is a bug from jdk 1.8: when a command fails, you can't have a result
code to 0.
We nned to open/track this *regression*.
> IT failures with Jdk 8 (EA)
> ---------------------------
>
> Key: MJARSIGNER-30
> URL: https://jira.codehaus.org/browse/MJARSIGNER-30
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Herve Boutemy
>
> see
> https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/modules
> {noformat}[INFO] --- maven-invoker-plugin:1.7:verify (integration-test) @
> maven-jarsigner-plugin ---
> [INFO] -------------------------------------------------
> [INFO] Build Summary:
> [INFO] Passed: 7, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -------------------------------------------------
> [ERROR] The following builds failed:
> [ERROR] * verify-fail/pom.xml
> [INFO] -------------------------------------------------{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
