[
https://issues.apache.org/jira/browse/MJARSIGNER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864993#comment-16864993
]
Andrew Peter Marlow commented on MJARSIGNER-41:
-----------------------------------------------
I just came across the ticket but have raised another one (before I knew of
this one), at https://issues.apache.org/jira/browse/MJARSIGNER-59, that covers
the same ground. In it I draw a parallel between the eclipse jarsigner plugin
and what I would like to see for maven. Looks like more work has been done on
this ticket though, since it has a patch. Let's hope it gets adopted.
> "maxtries" option for maven-jarsigner-plugin
> --------------------------------------------
>
> Key: MJARSIGNER-41
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-41
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
> Affects Versions: 1.3.2, 1.4
> Reporter: Gene Smith
> Priority: Minor
> Attachments: MJARSIGNER-41-addmaxtries.patch
>
>
> The actual jar signing is usually very reliable exercise in mathematics,
> which only fails on external resources.
> But connecting to the "Time Stamp Authority" is not no so reliable. When
> network issues can cause intermittent failures in jar signing during our long
> middle of the night builds it causes, out of size problems for our build
> process.
>
> I will present a patch which adds a "maxtries" parameter, to allow for
> repeated attempts. I considered but did not add a "retrydelay", as the
> overhead of the command process is a non-trivial delay. If whoever applies
> the patch feels "retrydelay" is desirable, they can add it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
