[GRADLE-476] Add configure-by-map functionality for our domain object container. Created: 12/May/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Won't Fix Votes: 0


This is from a mail from Steve Appling.

The proposal was:
configurations {
newConf extends: compile, transitive: true
// alternatively

Unknown macro: { extends = compile transitive = true }

existingConf transitive: true

The map based syntax does not appear to work - I'm hoping this is just not implemented yet, because it is nice and concise

The more verbose syntax options that works are:
configurations {

Unknown macro: { extendsFrom compile //or extendsFrom = [compile] transitive = true }


The following, however, does not work
configurations {

Unknown macro: { extendsFrom = compile transitive = true }


Configuration.setExtendsFrom takes a Set of superConfigs not a single one. This is awkward and most usages will probably have only a single parameter. Perhaps this should work with both a list and a single Configuration as was discussed for flatDir earlier today.

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