# Buildship, eclipse plug-in, multiproject builds

**URL:** <https://discuss.gradle.org/t/buildship-eclipse-plug-in-multiproject-builds/24030>\
**Category:** Buildship\
**Tags:** buildship\
**Created:** [September 11, 2017, 12:37am UTC](https://discuss.gradle.org/t/buildship-eclipse-plug-in-multiproject-builds/24030 "2017-09-11T00:37:25Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![st\_oehme](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/st_oehme/32/5249_2.png) [@st\_oehme](https://discuss.gradle.org/u/st_oehme)\
**Post date:** [September 11, 2017, 12:40pm UTC](https://discuss.gradle.org/t/buildship-eclipse-plug-in-multiproject-builds/24030/5 "2017-09-11T12:40:07Z")

</div>

> [@andreasb70](#):
>
> Is that what you mean by “customization of the Eclipse model”?

Exactly 🙂

> [@andreasb70](#):
>
> Is the correct procedure?

No, the developer should use “Import Gradle Project”.

> [@andreasb70](#):
>
> Running “gradle eclipse” from the root project is blazing fast, while right clicking on the root project and choosing “Gradle -\>refresh gradle project” takes forever with my 100 projects build

It should be exactly the same, can you reproduce this with a project you can share?

> [@andreasb70](#):
>
> Still to be able to open the subprojects (now “cleaned”) in eclipse and work on them I need to run the “Eclipse” task from the Gradle Tasks view, right?

No, the subprojects will be imported together with the root and should be ready to use.

---

_[View the full topic](https://discuss.gradle.org/t/buildship-eclipse-plug-in-multiproject-builds/24030)._