I think the gradle-wrapper.jar should be maintained inside the code base as an exceptional thing, otherwise it would be quite painful to administer the system.
The gradle wrapper is difficult to download and obtain, and is usually provided using a gradle command (installed gradle on the platform. So it's best to just keep it in. On Sun, Jun 23, 2019 at 4:58 PM Mathieu Lirzin <[email protected]> wrote: > > Mathieu Lirzin <[email protected]> writes: > > > Nicolas Malin <[email protected]> writes: > > > >> Jacques suggests to store the gradle-wrapper.jar on own tools > >> repository source[3] and download through viewvc with one wrapper by > >> stable branch. > >> I suggest to download it from gradle community on github and store the > >> release to download in own code source[4] > >> > >> Your opinion ? or other idea ? > > > > IMO storing Gradle binary releases in our own infrastructure is too much > > trouble. If we don't trust Gradle binaries to continue to be available > > in the future, we maybe should use another build system instead of > > keeping trying to keep our copies of its binary releases. No? > > I overlooked that we were not speaking of downloading the binary > releases, but only of the “gradle-wrapper.jar” which should already be > avaibable in our VCS branches in order to comply with Gradle wrapping > recommendations as I advocated in my previous mail. > > Given that each release archive can point to its corresponding > repository branch to find its associated “gradle-wrapper.jar”, it is > basically free in term of maintenance. Then I agree with Jacques option. > > Sorry for the confusion. > > -- > Mathieu Lirzin > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
