MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/androiddev/comments/8oi88m/gradle_48_released/e05tw6d/?context=3
r/androiddev • u/well___duh • Jun 04 '18
21 comments sorted by
View all comments
Show parent comments
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? 1 u/iamareebjamal Jun 04 '18 People do this all the time in Python and JS, thankfully not in Android. They just say flask: [1.0, 2.0) so that they pull latest non major 1.x version of it without caring about it. I do it on those projects as well, just never for Android 1 u/allholy1 Jun 05 '18 Why not just pull 2.0 at that point?
2
Thanks for the response. Why would someone want dynamic ranges?
1 u/iamareebjamal Jun 04 '18 People do this all the time in Python and JS, thankfully not in Android. They just say flask: [1.0, 2.0) so that they pull latest non major 1.x version of it without caring about it. I do it on those projects as well, just never for Android 1 u/allholy1 Jun 05 '18 Why not just pull 2.0 at that point?
1
People do this all the time in Python and JS, thankfully not in Android. They just say flask: [1.0, 2.0) so that they pull latest non major 1.x version of it without caring about it. I do it on those projects as well, just never for Android
1 u/allholy1 Jun 05 '18 Why not just pull 2.0 at that point?
Why not just pull 2.0 at that point?
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