[GRADLE-949] A subproject will check the cache for a jar instead of the jar produced by the dependency Created: 27/May/10  Updated: 04/Jan/13  Resolved: 24/Nov/10

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

Type: Bug
Reporter: Ernesto Morales-Perea Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Issue Links:
Duplicated by GRADLE-962 When building a project, Gradle tries... Resolved


I'm not sure if this is intended behavior, but the following scenario occurs:

Project A has subprojects project(':sub1') and project(':sub2') that produce jars. :sub1 depends on :sub2 under the compile configuration. Project A is built and its jars are uploaded.

Project B has dependencies on both jars produced by A. Project B is built successfully and brings A's jars into the gradle cache.

Project A's :sub2 has code changes and is rebuilt with compileJava. Project A fails to build because :sub1 is now referencing the jars of :sub2 in the cache instead of the jar created by the :sub1:jar task.

I'm expecting :sub1 to reference the jar changes in :sub2:jar and not what was uploaded to the archives.

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