Eclipse Plugin and Unresolved Dependencies

If Gradle fails to resolve a dependency, there is no error when running “gradle eclipse”: instead, it generates .classpath files with bad file paths.

This is using Gradle 1.8.

This is desired. Many users want to be able to import the project into the IDE even though some dependencies are unresolved.

We do however, should print some fat warning if this happens. We already have a jira for this.

Thanks for reporting!