>How about adding wrapper.jar to our project source code?
This has been discussed on the original issue, with links to other sources:
https://github.com/apache/lucene/issues/10306
I think it's more consistent to have the CI actually retry those
source links for the wrapper... makes errors
Hi,
How about adding wrapper.jar to our project source code?
then, exclude this jar when we release the source code, Of course, since there
is no wrapper.jar in the released source package, it is necessary to download
it just at this time.
Another question, why don't we use the official
+1. Updated the patch.
On Tue, Sep 13, 2022 at 9:24 AM Robert Muir wrote:
>
> Can also potentially avoid them and reduce the amount of back-n-forth
> by pulling from the ultimate URL instead of redirecting around:
>
Can also potentially avoid them and reduce the amount of back-n-forth
by pulling from the ultimate URL instead of redirecting around:
https://raw.githubusercontent.com/gradle/gradle/v7.3.3/gradle/wrapper/gradle-wrapper.jar
On Tue, Sep 13, 2022 at 3:20 AM Dawid Weiss wrote:
>
> These 500/503s are
These 500/503s are getting annoying. Let's see if it's something that
can be fixed with a simple retry mechanism.
https://github.com/apache/lucene/pull/11766
Dawid
On Tue, Sep 13, 2022 at 7:59 AM Apache Jenkins Server
wrote:
>
> Build:
>
