[GRADLE-164] Artifact dependency unresolved when custom destinationDir is used. Created: 21/Jul/08  Updated: 04/Jan/13  Resolved: 31/Jul/08

Status: Resolved
Project: Gradle
Affects Version/s: 0.2
Fix Version/s: 0.3

Type: Bug
Reporter: Pieter Smit Assignee: Hans Dockter
Resolution: Fixed Votes: 0


The following happens when the destinationDir is changed:

subprojects {
task("${project.name}_jar").destinationDir = file(distDir)

This causes the libs task to output all my subprojects generated jars in a single directory of my choice, which was what I intended. What I didn't intend was the following:

missing artifact com.bla#bla-interface;1.0!bla-interface.jar:
/home/pieter/development/trunk/bla-interface/build/bla-interface-1.0.jar file does not exist
/home/pieter/development/trunk/bla-interface/build/distributions/bla-interface-1.0.jar file does not exist
published ivy to /home/pieter/development/trunk/build-resolver/com.bla/bla-interface/1.0/ivys/ivy.xml

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