[GRADLE-640] rename Project.getDependencies Created: 17/Sep/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Philip Crotwell Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Project.getDependencies() doesn't actually allow access to the dependencies, but rather is a way to add dependencies to the project. Would be less confusing to rename it, perhaps getDependencyHandler() or getDependencyAdder() .

Also, the current javadoc is confusing, as it says that it "Returns the dependencies of this project." which it doesn't actually do.

 Comments   
Comment by Hans Dockter [ 12/Oct/09 ]

I have changed the javadoc. For 0.9 we plan to refactor the dependencies API. We want to get rid of the configurations and turn them into composite dependencies. Then you can do:

dependencies.compile.files

Which I guess will make this issue obsolete as dependencies then do what you expect it to do. I leave the issue open until the work is actually done.

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 11:35:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.