[
https://issues.apache.org/jira/browse/MJARSIGNER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763408#comment-17763408
]
Herve Boutemy edited comment on MJARSIGNER-68 at 9/10/23 11:03 AM:
-------------------------------------------------------------------
failing IT log ends with
{noformat}
[DEBUG] The jar will be treated as unsigned, because it is signed with a weak
algorithm that is now disabled.
...
[INFO] -------------------------------------------------
[WARNING] The following builds failed:
[WARNING] * verify-fail/pom.xml
[INFO] -------------------------------------------------
{noformat}
I suppose old JDKs don't have this rejected weak algorithm, but newer used by
CI are choking (for good reasons)
was (Author: hboutemy):
failing IT log ends with
{noformat}
[DEBUG] The jar will be treated as unsigned, because it is signed with a weak
algorithm that is now disabled.
{noformat}
I suppose old JDKs don't have this rejected weak algorithm, but newer used by
CI are choking (for good reasons)
> CI is broken
> ------------
>
> Key: MJARSIGNER-68
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-68
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
> Reporter: Elliotte Rusty Harold
> Priority: Blocker
>
> src/it/verify-fail fails on the CI though it seems to pass locally. As best
> I've been able to figure out the failing output is not saved in the CI
> environment anywhere for inspection and debugging. Perhaps someone with more
> access to the backend can retrieve the log files from this test and figure
> out what's going wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
