[GRADLE-2521] SelfResolvingDependencies and builtBy Created: 15/Oct/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

Problems:

  • the 'builtBy' task hooked to the SelfResolvingDependencies is not executed when iterating the files of the configuration. I think it is slightly unexpected.
  • if the user replaces 'files' with 'fileTree' in the dependencies section he may end up with different results. I would think FileCollection neatly abstracts out differences between tree and file list.

See the example build file below. The way to reproduce is run (separately):

gradle depsByFileTree
gradle depsByFileCollection

The expected output is the same for both executions. However, the output is different.

apply plugin: 'base'

configurations {
  byCollection
  byTree
}

def byFileCollection = files(["$buildDir/foo/1.jar", "$buildDir/foo/2.jar"]) {
  builtBy "foo"
}

def byFileTree = fileTree("$buildDir/foo") {
  builtBy "foo"
}

dependencies {
  byCollection byFileCollection
  byTree byFileTree 
} 

task foo << {
  file("$buildDir/foo").mkdirs()
  file("$buildDir/foo/1.jar").createNewFile()
  file("$buildDir/foo/2.jar").createNewFile()
}

task depsByFileTree(dependsOn: clean) << {
  println "Dependencies by file tree"
  configurations.byTree.each { println it }
}

task depsByFileCollection(dependsOn: clean) << {
  println "Dependencies by file collection"
  configurations.byCollection.each { println it }
}


 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:24:12 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.