# What is latest recommendation of Groovy Eclipse Pluigin support to use with Buildship?

**URL:** <https://discuss.gradle.org/t/what-is-latest-recommendation-of-groovy-eclipse-pluigin-support-to-use-with-buildship/22189>\
**Category:** Buildship\
**Created:** [April 3, 2017, 1:46am UTC](https://discuss.gradle.org/t/what-is-latest-recommendation-of-groovy-eclipse-pluigin-support-to-use-with-buildship/22189 "2017-04-03T01:46:25Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![David\_Karr](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/david_karr/32/145_2.png) [@David\_Karr](https://discuss.gradle.org/u/David_Karr)\
**Post date:** [April 5, 2017, 3:30pm UTC](https://discuss.gradle.org/t/what-is-latest-recommendation-of-groovy-eclipse-pluigin-support-to-use-with-buildship/22189/8 "2017-04-05T15:30:03Z")

</div>

> [@Lance](#):
>
> Please keep in mind that editing maven pom.xml in eclipse is also pretty much a plain text editor

To be fair, that’s an oversimplification. Completion on configuration elements per plugin, navigation to parent pom, form-based pom editor, and the search facility for dependencies, are all useful features. I would almost consider creating a dummy maven project in my workspace just for that last feature.

---

_[View the full topic](https://discuss.gradle.org/t/what-is-latest-recommendation-of-groovy-eclipse-pluigin-support-to-use-with-buildship/22189)._