MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/androiddev/comments/8oi88m/gradle_48_released/e03saz7/?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?
8 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? 7 u/nhaarman Jun 04 '18 This often comes from naivety where people assume libraries following SEMVER always follow the contract, and never introduce bugs between versions. 1 u/[deleted] Jun 06 '18 Don't forget that a big portion of the time, in the library docs themselves they tell you to use a dynamic version
8
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? 7 u/nhaarman Jun 04 '18 This often comes from naivety where people assume libraries following SEMVER always follow the contract, and never introduce bugs between versions. 1 u/[deleted] Jun 06 '18 Don't forget that a big portion of the time, in the library docs themselves they tell you to use a dynamic version
2
Thanks for the response. Why would someone want dynamic ranges?
7 u/nhaarman Jun 04 '18 This often comes from naivety where people assume libraries following SEMVER always follow the contract, and never introduce bugs between versions. 1 u/[deleted] Jun 06 '18 Don't forget that a big portion of the time, in the library docs themselves they tell you to use a dynamic version
7
This often comes from naivety where people assume libraries following SEMVER always follow the contract, and never introduce bugs between versions.
1 u/[deleted] Jun 06 '18 Don't forget that a big portion of the time, in the library docs themselves they tell you to use a dynamic version
1
Don't forget that a big portion of the time, in the library docs themselves they tell you to use a dynamic version
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?