gradlew - How can I always use the latest version of custom gradle wrapper -




i have custom gradle wrapper used company wide. wrapper published artifactory. has version 1.0. distributionurl in gradle-wrapper.properties pointing artifactory , version 1.0.

when create version 1.1 of custom wrapper there possibility project use wrapper automatically pull newest version or need change distributionurl in each project?

not know of, seems bad idea: 1 of great things in gradle wrapper allows sure project uses gradle version has been developed , 'just works'. having moving version defeat that.

for sake of argument, suppose having fixed url distributionurl, , change gradle distribution on web server, keeping same fixed name (not sure how gradle wrapper behave, , again bad idea).

instead, have seed project (in git) update url, , propagate changes in each project merging seed. automated, , bonus can track when gradle version changed each project (and potentially broke build) because have corresponding commits.





wiki

Comments

Popular posts from this blog

Asterisk AGI Python Script to Dialplan does not work -

python - Read npy file directly from S3 StreamingBody -

kotlin - Out-projected type in generic interface prohibits the use of metod with generic parameter -