[GRADLE-2742] DependencyHandler support dependency notation list with a configure closure Created: 09/Apr/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Think Wu Assignee: Unassigned
Resolution: Won't Fix Votes: 0


DependencyHandler should support multiple dependency notations followed by a configure closure, like grails does:

compile('group1:artifact1:ver1', 'group2:artifact2:ver2')

{ exclude group: 'excluded-group', module: 'excluded-artifact' }

This will make build script more concise.

Comment by Think Wu [ 09/Apr/13 ]

format the code snippet

compile('group1:artifact1:ver1', 'group2:artifact2:ver2') {
 exclude group: 'excluded-group', module: 'excluded-artifact'
Comment by Think Wu [ 21/Apr/13 ]

The above exclusion mighty be done by configuration-level exclude.

But I think it make sense to allow applying a config to multiple dependencies, for example:

compile('group1:artifact1:ver1', 'group2:artifact2:ver2') {
  force = true
  transitive = false

Since we can write "compile dep, dep", and "compile dep, config", it's reasonable to guess that we should also be able to write "compile dep, dep, config", isn't it?

Comment by Think Wu [ 22/Apr/13 ]

Pull Request opened on GitHub.

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:30:15 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.