[GRADLE-641] eclipse task fails in multiproject Created: 17/Sep/09  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.9-rc-1

Type: Improvement
Reporter: Philip Crotwell Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Issue Links:
dependent on GRADLE-616 Problems Resolving external dependenc... Resolved


In a multiproject that has not been been built yet, the eclipse Cp task fails to generate a .classpath file for eclipse if the jars from dependent multiprojects are not yet in the internal-repository. As gradle Project dependencies are mapped to eclipse "projects on the build path", there should be no need to resolve the output jars.

THis might be related to GRADLE-576

To reproduce, add usePlugin('eclipse') to samples/userguide/multiproject/dependencies/java/build.gradle and then run 'gradle eclipse' from the api folder. It generates this error:

$ gradle eclipse
:: problems summary ::
module not found: org.gradle.sample#shared;1.0

==== clientModule: tried

==== internal-repository: tried


– artifact org.gradle.sample#shared;1.0!shared.jar:





:: org.gradle.sample#shared;1.0: not found


Build failed with an exception.
Run with -s or -d option to get more details. Run with -f option to get the full (very verbose) stacktrace.

Empty build file

Execution failed for task ':api:eclipseCp'.
Cause: Could not resolve all dependencies for configuration 'testRuntime':

  • unresolved dependency: org.gradle.sample#shared;1.0: not found


Total time: 9.765 secs

Gradle 0.8-20090728100643+1000

Gradle buildtime: Tuesday, July 28, 2009 10:06:43 AM EST
Groovy: 1.6.3
Ant: Apache Ant version 1.7.0 compiled on December 13 2006
Ivy: 2.1.0-rc2
Java: 1.5.0_19
JVM: 1.5.0_19-138
JVM Vendor: "Apple Computer, Inc."
OS Name: Mac OS X

Generated at Wed Jun 30 11:35:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.