It’s not quite the same as a static URL that could be put in a gradle-wrapper.properties file but with some CI trickery combined with gradle wrapper --gradle-version you could probably automate this.
@idlsoft I can only think of a single use case where this would be helpful: for verifying if a bug was fixed before another RC has been released. Is that your use case?
That’s exactly it. New RCs are released in one week intervals, the bug I reported has been fixed 2 days after RC2,
I tried the nightly build, hoping that all fixes going to the release branch automatically get merged into master.
That’s not the case, unfortunately, so I’m stuck, and have to wait for the next RC to continue my testing.
Building locally is not an option, because of a firewall.
As @bmuschko mentioned, we don’t publish nightlies from the release branch. We can however manually create a snapshot release. I’ve gone ahead and done this so you can test this latest fix.
I suppose we could start doing nightlies. We’d have to potentially tweak some stuff on our end to ensure we only publish release branch snapshots while the branch is “active” but that probably wouldn’t be too difficult.