# Minimum Gradle version for developing plugins

**URL:** <https://discuss.gradle.org/t/minimum-gradle-version-for-developing-plugins/5191>\
**Category:** Old Forum Archive\
**Created:** [December 3, 2014, 8:00pm UTC](https://discuss.gradle.org/t/minimum-gradle-version-for-developing-plugins/5191 "2014-12-03T20:00:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Schalk\_Cronje](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/schalk_cronje/32/6511_2.png) [@Schalk\_Cronje](https://discuss.gradle.org/u/Schalk_Cronje)\
**Post date:** [December 3, 2014, 8:00pm UTC](https://discuss.gradle.org/t/minimum-gradle-version-for-developing-plugins/5191/1 "2014-12-03T20:00:00Z")

</div>

As we are now firmly on the 2.x track I was wondering what the recommendation should be for building a plugin as far as Gradle version goes.

Should plugin developers build against 2.0 (unless they actually want new functionality available in 2.2) ?

---

<div class="post-metadata">

**Author:** ![luke\_daley](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/luke_daley/32/9890_2.png) [@luke\_daley](https://discuss.gradle.org/u/luke_daley)\
**Post date:** [December 3, 2014, 11:21pm UTC](https://discuss.gradle.org/t/minimum-gradle-version-for-developing-plugins/5191/2 "2014-12-03T23:21:00Z")

</div>

That’s a good strategy.

---

<div class="post-metadata">

**Author:** ![Schalk\_Cronje](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/schalk_cronje/32/6511_2.png) [@Schalk\_Cronje](https://discuss.gradle.org/u/Schalk_Cronje)\
**Post date:** [December 4, 2014, 11:50am UTC](https://discuss.gradle.org/t/minimum-gradle-version-for-developing-plugins/5191/3 "2014-12-04T11:50:00Z")

</div>

As an additional recommendation for people wanting to test a Gradle 2.0 plugin against Gradle 1.x is to conditionally include the ‘groovy-backports-compat23’ dependency.