[
https://issues.apache.org/jira/browse/MJARSIGNER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656746#comment-17656746
]
Andrew Peter Marlow commented on MJARSIGNER-59:
-----------------------------------------------
Is there any chance that Thorsten's patch can be done officially please?
> increase reliability when contacting timestamp service over unreliable network
> ------------------------------------------------------------------------------
>
> Key: MJARSIGNER-59
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-59
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Andrew Peter Marlow
> Priority: Major
> Attachments:
> 0001-Added-retries-upon-failure-and-support-multiple-TSA-.patch
>
>
> {color:#000000}The signing plugin fails in the presence of an unreliable
> network. Could retries be added please? I am thinking of something like up to
> 3 retries,{color} sleeping for one second between.{color:#000000}
>
>
>
> I have just started to use this plugin and this is a major issue. It makes
> my overnight builds fail more often than not. Prior to me making this change
> the project produced unsigned jars during the java build and later on via a
> python script added the signing. Once the {color}
> {color:#000000}unreliable network issue was identified the python script was
> changed, adding retries (the network issue will most likely never be fixed).
> These retries in the python script fixed the issue. Now I am using the maven
> plugin the issue is back.{color}
>
> Some people might think that if this is happening in a wired corporate
> network then the network issue ought to be identified and resolved by the
> corporation. Well, maybe. But this issue could easily strike on networks that
> are inherently less reliable such as wifi and mobile. So I really think that
> the retries should be there to cater for that.
>
> {color:#000000} {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
