We have a relatively large team all using slightly different versions of Gradle. All of the team are required to be within a specific Gradle version subset (eg. 0.9.x) but beyond that, they are welcome to use what they want.
I simply wanted to emphasize that since, I believe, this to be fairly common practice it would not be good to remove functionality between minor versions of Gradle. For example, I would be fine with the removal of the "allTasks()" method in version 1.0.x but not in 0.9.3. I would expect my team to be able to use any 0.9.x version of Gradle without issues but that they should be more cautious if moving to a new major release (such as 1.0). In a post Gradle 1.0 world, I would also expect to be able to bounce between 1.0.x versions without issue but may show caution when moving to a 1.1.x version. Perhaps I am confused about major and minor versions as it relates to Gradle. For the issue I am inquiring about, I wanted to know if my assumptions are correct. Will this functionality actually be removed in version 1.0 and beyond or do I have to lock my team to version 0.9.0 - 0.9.2? --Ken On Mon, Feb 7, 2011 at 9:21 AM, Peter Niederwieser <[email protected]>wrote: > > Are you using multiple Gradle versions for the same build? If so, why? > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Founder, Spock Framework > http://spockframework.org > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Gradle-deprecation-warning-tp3374497p3374505.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
