[GRADLE-616] Problems Resolving external dependencies when project dependencies are used Created: 02/Sep/09  Updated: 04/Jan/13  Resolved: 24/Nov/10

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

Type: Bug
Reporter: Steve Appling Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Attachments: Text File another-project.patch    
Issue Links:
dependent
dependent by GRADLE-641 eclipse task fails in multiproject Resolved

 Description   

We have encountered problems while trying to add a subproject for the UI. I am seeing this problem with gradle's own build.

I have attached a simple patch that can reproduce the problem:

It adds a new sub-project, "another". The "another" project has a compile configuration project dependency on gradle-core.
Run "gradlew ide" to resolve the external dependencies and copy them to the lib directory. This will cause:

>gradlew ide
:ide
:another:ide
:: problems summary ::
:::: WARNINGS
module not found: org.gradle#gradle-core;0.8-20090902170257-0400

==== clientModule: tried

==== internal-repository: tried

C:\OpenSource\gradle\committer\.gradle\internal-repository/org.gradle/gradle-core/ivy-0.8-20090902170257-0400.xml

– artifact org.gradle#gradle-core;0.8-20090902170257-0400!gradle-core.jar:

C:\OpenSource\gradle\committer\.gradle\internal-repository/org.gradle/gradle-core/jars/gradle-core-0.8-20090902170257-0400.jar

==== MavenRepo: tried

http://repo1.maven.org/maven2/org/gradle/gradle-core/0.8-20090902170257-0400/gradle-core-0.8-20090902170257-0400.pom

– artifact org.gradle#gradle-core;0.8-20090902170257-0400!gradle-core.jar:

http://repo1.maven.org/maven2/org/gradle/gradle-core/0.8-20090902170257-0400/gradle-core-0.8-20090902170257-0400.jar

==== sf_gradleRepo: tried

– artifact org.gradle#gradle-core;0.8-20090902170257-0400!gradle-core.jar:

http://gradle.sourceforge.net/gradleRepo/org.gradle/gradle-core/jars/gradle-core-0.8-20090902170257-0400.jar

::::::::::::::::::::::::::::::::::::::::::::::

:: UNRESOLVED DEPENDENCIES ::

::::::::::::::::::::::::::::::::::::::::::::::

:: org.gradle#gradle-core;0.8-20090902170257-0400: not found

::::::::::::::::::::::::::::::::::::::::::::::

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

Build file 'C:\OpenSource\gradle\committer\subprojects\another\build.gradle'

Execution failed for task ':another:ide'.
Cause: Could not resolve all dependencies for configuration 'testRuntime':

  • unresolved dependency: org.gradle#gradle-core;0.8-20090902170257-0400: not found

BUILD FAILED

Total time: 17.453 secs

 Comments   
Comment by Hans Dockter [ 03/Sep/09 ]

The ide task does depend now on configurations.runtime.buildDependencies

Comment by Hans Dockter [ 03/Sep/09 ]

Of course my solution does not make much sense. You don't want to depend for the ide task on building the subprojects. There is no good solution for this yet. In the case of the ide task we should go back to configuration.copy until we have a better solution. For a full discussion of this issue, see: http://markmail.org/thread/te5ko6c5qtt2y22d

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