Thanks Nicolas,
The reason I finally decided to get this way is commented here:
https://s.apache.org/Vsy3
In few words, we can no longer find the 2.13 wrapper version at https://github.com/gradle/gradle/tree/v2.13/gradle/wrapper like we still can for 3.2.1
and 5.0
Our stable release relies on it. It's a blocker. And I fear the same could happen in future for newer OFBiz releases. That's why I prefer to keep
copies in our repo.
BTW, Swapnil raised a new issue yesterday. With the current solution what to do
for our users when we upgrade Gradle on the trunk?
I suggested a simple solution, so better to read at least the last comments,
thanks.
As always, all ideas are welcome
Jacques
Le 22/06/2019 à 16:53, Nicolas Malin a écrit :
Hello,
With the commit r1861766 on trunk[1], I removed gradle-wrapper.jar from source (OFBIZ-10145[2]) and now we download it at the first time when you
run 'gradlew'. It's fast download (55ko) so normally transparent
You can try yourself after update your trunk, it's esay :) .
Jacques and me have a different vision on where we should download the jar and before continue to propagate the deleting on stable branches, I like
to get your opinion.
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 ?
Nicolas
[1] https://svn.apache.org/viewvc?diff_format=h&view=revision&revision=1861766
[2] https://issues.apache.org/jira/browse/OFBIZ-10145
[3] https://svn.apache.org/repos/asf/ofbiz/tools/Buildbot/Gradle/Wrapper/trunk/
[4] https://github.com/gradle/gradle/tree/v5.0.0/gradle/wrapper
