[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: |
|
Description |
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 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 ==== clientModule: tried ==== internal-repository: tried /private/var/automount/home/crotwell/dev/gradle/src/samples/userguide/multiproject/dependencies/java/.gradle/internal-repository/org.gradle.sample/shared/ivy-1.0.xml – artifact org.gradle.sample#shared;1.0!shared.jar: /private/var/automount/home/crotwell/dev/gradle/src/samples/userguide/multiproject/dependencies/java/.gradle/internal-repository/org.gradle.sample/shared/jars/shared-1.0.jar :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: org.gradle.sample#shared;1.0: not found :::::::::::::::::::::::::::::::::::::::::::::: Build failed with an exception. Empty build file Execution failed for task ':api:eclipseCp'.
BUILD FAILED Total time: 9.765 secs ------------------------------------------------------------ Gradle buildtime: Tuesday, July 28, 2009 10:06:43 AM EST |