[GRADLE-1332] `gradle dependencies` reports do not include dependencies from flat directories Created: 21/Jan/11  Updated: 16/Jan/17  Resolved: 16/Jan/17

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

Type: Bug
Reporter: Matthias Assignee: Unassigned
Resolution: Duplicate Votes: 10


 Description   

Define a dependency block like this one:

dependencies

{ compile fileTree(dir: "libs", include: '*.jar') }

Run this on the command line:
$gradle dependencies

Output:
compile - Classpath for compiling the sources.
No dependencies

That's highly misleading, since configurations.compile.files in fact does include the dependencies from the libs dir. This made me think my build files are wrong, since I trusted the dependencies report to reflect what will be in the compile classpath.

I could imagine that a lot of people new to Gradle would struggle with this.

 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 Mauro Molinari [ 15/Nov/16 ]

I think this is a duplicate of GRADLE-2269 (or the other way around).

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