[
https://jira.codehaus.org/browse/MJARSIGNER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356822#comment-356822
]
Gene Smith commented on MJARSIGNER-41:
--------------------------------------
I think Michael is right that Camel Case is appropriate here.
I use it personally, but I have seen "maxtries" and "mintries" in all lower
case so many times that that it is the way I tend to type them, and I did not
even think about the fact "maxtries" might be two words for camelcase.
> "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)
