[GRADLE-2735] Cannot create configuration named 'container' using standard configurations syntax Created: 02/Apr/13 Updated: 03/Apr/13 Resolved: 02/Apr/13 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.5 |
| Fix Version/s: | 1.6-rc-1 |
| Type: | Bug | ||
| Reporter: | Daz DeBoer | Assignee: | Peter Niederwieser |
| Resolution: | Fixed | Votes: | 0 |
| Issue Links: |
|
||||||||
| Known Issue Of: | |||||||||
| Description |
|
Due to a private field named "container" on org.gradle.api.internal.NamedDomainObjectContainerConfigureDelegate, the following code no longer creates the expected configuration:
configurations {
container
}
The workaround is to force gradle to recognise this as a creation method by adding an empty closure parameter:
configurations {
container {}
}
|
| Comments |
| Comment by Daz DeBoer [ 02/Apr/13 ] |
|
Fixed in https://github.com/gradle/gradle/commit/57d1261b3358e5e7238a5534748459170af56407 |