[GRADLE-2921] Adding dependencies to extended configuration does not error if extending configuration has already been resolved Created: 14/Oct/13 Updated: 28/Aug/14 Resolved: 25/Aug/14
|Reporter:||Gradle Forums||Assignee:||Szczepan Faber|
Consider this example:
This does the correct thing, it will error, informing the user "You can't change a configuration which is not in unresolved state!"
This doesn't error. I argue this should, since this should attempt to implicitly change the runtime configuration which is not in an unresolved state. The lack of an error makes it very hard to track down bugs related to altering configurations in tasks to be used later on in the build, a very useful feature of gradles configuration model.