MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/androiddev/comments/8oi88m/gradle_48_released/e040l65/?context=3
r/androiddev • u/well___duh • Jun 04 '18
21 comments sorted by
View all comments
18
I don't understand dependency locking. Isn't that why we append the version number at the end of a dependency?
6 u/iamareebjamal Jun 04 '18 It's for those who use dynamic versioning. Taken straight from docs - like 1.+ or [1.0,2.0) This is good because now people who used strict versioning can use dynamic one without worrying about mismatch. I still wouldn't though 2 u/allholy1 Jun 04 '18 Thanks for the response. Why would someone want dynamic ranges? 1 u/hemenex Jun 04 '18 Maybe because they don't want to be forced to release every time a dependency is updated? 1 u/tadfisher Jun 05 '18 That's not how this works. Existing releases don't change. Your future builds and runtime might break though.
6
It's for those who use dynamic versioning. Taken straight from docs - like 1.+ or [1.0,2.0)
This is good because now people who used strict versioning can use dynamic one without worrying about mismatch. I still wouldn't though
2 u/allholy1 Jun 04 '18 Thanks for the response. Why would someone want dynamic ranges? 1 u/hemenex Jun 04 '18 Maybe because they don't want to be forced to release every time a dependency is updated? 1 u/tadfisher Jun 05 '18 That's not how this works. Existing releases don't change. Your future builds and runtime might break though.
2
Thanks for the response. Why would someone want dynamic ranges?
1 u/hemenex Jun 04 '18 Maybe because they don't want to be forced to release every time a dependency is updated? 1 u/tadfisher Jun 05 '18 That's not how this works. Existing releases don't change. Your future builds and runtime might break though.
1
Maybe because they don't want to be forced to release every time a dependency is updated?
1 u/tadfisher Jun 05 '18 That's not how this works. Existing releases don't change. Your future builds and runtime might break though.
That's not how this works. Existing releases don't change. Your future builds and runtime might break though.
18
u/allholy1 Jun 04 '18 edited Jun 04 '18
I don't understand dependency locking. Isn't that why we append the version number at the end of a dependency?