[GRADLE-2340] API consistency - dependencies expressed with 'group' and 'name', excludes with 'group' and 'module' Created: 08/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-3
Fix Version/s: None

Type: Improvement
Reporter: wujek srujek Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Hi. Take a look at the following snippet:


{ testCompile.exclude group: 'junit', module: 'junit' }


{ groovy group: 'org.codehaus.groovy', name: 'groovy', version: '1.8.6' testCompile group: 'org.testng', name: 'testng', version: '6.5.2' testCompile group: 'org.mockito', name: 'mockito-core', version: '1.9.0' }

The API is inconsistent: deps use 'group' and 'name' attributes, but excludes use 'group' and 'module'. This is a cause of build bugs that are not that require the user to go and google and dig in the API doc to find the right syntax, whereas it could be made consistent and what users expect.


Comment by wujek srujek [ 15/Jun/13 ]

Hi. It's been a year without even a comment. Any thoughts on the API inconsistency? Or is it by design? Would love to know.

Comment by wujek srujek [ 15/Jun/13 ]

Is anybody getting any updates to this bug? There is no assignee and no other watchers as me, so maybe nobody even noticed this ticket?

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