[
https://jira.codehaus.org/browse/MJARSIGNER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gene Smith updated MJARSIGNER-41:
---------------------------------
Attachment: MJARSIGNER-41-addmaxtries.patch
This patch adds an optional "maxtries" parameter to AbstractJarsignerMojo.java,
and wraps the command execution in a do//while loop with a success check and a
log line on failure.
...........
working in a repository identified by:
$ git remote -v
origin git://github.com/apache/maven-plugins.git (fetch)
origin git://github.com/apache/maven-plugins.git (push)
$ git branch
* trunk
$ git log -5 --oneline
3c61c42 MJARSIGNER-41 - "maxtries" option for maven-jarsigner-plugin
300ba8c [MRRESOURCES-82] Upgrade to maven-plugins parent version 27
0a9c2fe removed configuration now inherited from parent
b263fe8 [MJARSIGNER-40] Upgrade maven version to 2.2.1
ddd2478 [MJAR-191] Upgrade to maven-plugins parent version 27
> "maxtries" option for maven-jarsigner-plugin
> --------------------------------------------
>
> Key: MJARSIGNER-41
> URL: https://jira.codehaus.org/browse/MJARSIGNER-41
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
> Affects Versions: 1.4, 1.3.2
> 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
(v6.1.6#6162)
