# Unresolved manifest dependency

**URL:** <https://discuss.gradle.org/t/unresolved-manifest-dependency/22266>\
**Category:** Buildship\
**Created:** [April 7, 2017, 4:12pm UTC](https://discuss.gradle.org/t/unresolved-manifest-dependency/22266 "2017-04-07T16:12:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sc1478](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sc1478/32/4341_2.png) [@sc1478](https://discuss.gradle.org/u/sc1478)\
**Post date:** [April 7, 2017, 4:12pm UTC](https://discuss.gradle.org/t/unresolved-manifest-dependency/22266/1 "2017-04-07T16:12:53Z")

</div>

I meant to send this out a couple of days ago, but evidently it remained in my browser unsent.

In an attempt to resolve

> [@What is latest recommendation of Groovy Eclipse Pluigin support to use with Buildship?](https://discuss.gradle.org/t/what-is-latest-recommendation-of-groovy-eclipse-pluigin-support-to-use-with-buildship/22189/8):
>
> 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.

I have been dealing with someone who works on the Groovy plugin.

He asks me to inform you:  
Could you let Buildship project know that they have an unresolved  
dependency in their manifest for org.eclipse.buildship.core? I’ll try  
to find a way around this, but it is slowing me down.

> <https://github.com/groovy/groovy-eclipse/issues/277#issuecomment-291918495>
>
> My need for this plugin is primarily to write Gradle plugins in groovy.
> 
> There… is an issue, mostly cosmetic, that I can't solve. When this plugin is NOT installed, but the Buildship plugin IS installed, then the display of gradle buildscripts in the Project Explorer is correct (the gradle scripts have elephant icons).
> 
> !\[2017-04-03\_14-34-35\](https://cloud.githubusercontent.com/assets/15382550/24628536/513d3726-187c-11e7-8cec-ae38e8955dce.png)
> 
> But after installing this plugin then the display of gradle buildscripts in Project Explorer is incorrect (Big fat ugly exclamation mark for the gradle scripts in project explorer, but no error messages in the Markers tab or Problems tab).
> 
> !\[2017-04-03\_14-44-51\](https://cloud.githubusercontent.com/assets/15382550/24628553/62548e4c-187c-11e7-94ed-18b5952da74b.png)
> 
> This seems to be purely cosmetic but it's annoying. The gradle building within Eclipse is not affected. But, since I need to edit code for a gradle plugin, I want the groovy editor support, but it seems to mess up at least the cosmetics of the Eclipse Project Explorer.

So I’m letting you know.