jcompagner commented on PR #1:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1850085171
as i said, for us multiply TSA is way more important then retries, it just
need to roll over the TSA once
Because last week Thursday, 1 or 2 projects builds where brok
schedin commented on PR #1:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1850075000
@jcompagner: You have a good point. Since this pull request is now closed
(because most of the feature request was implemented in
https://github.com/apache/maven-jarsigner-plugi
elharo closed pull request #1: Implement maxTries parameter
URL: https://github.com/apache/maven-jarsigner-plugin/pull/1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsu
elharo commented on PR #1:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1850065065
superseded by https://github.com/apache/maven-jarsigner-plugin/pull/13
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
jcompagner commented on PR #1:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1849690136
that multi tsa is more important then just a retry, that is because if a tsa
service is not working then it can be not working for quite some time (not
minutes but more hours
schedin commented on PR #1:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1848967331
Since the multiple tsa URL suggestion by @jcompagner was a bit hidden (in
the comment of this pull request) I have written a dedicated ticket for it:
https://issues.apache.org/j
