# Resolved configurations can be modified in a multi-project build

**URL:** <https://discuss.gradle.org/t/resolved-configurations-can-be-modified-in-a-multi-project-build/729>\
**Category:** Old Forum Archive\
**Created:** [November 10, 2013, 5:40pm UTC](https://discuss.gradle.org/t/resolved-configurations-can-be-modified-in-a-multi-project-build/729 "2013-11-10T17:40:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![swpalmer](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/swpalmer/32/80_2.png) [@swpalmer](https://discuss.gradle.org/u/swpalmer)\
**Post date:** [November 10, 2013, 5:40pm UTC](https://discuss.gradle.org/t/resolved-configurations-can-be-modified-in-a-multi-project-build/729/1 "2013-11-10T17:40:00Z")

</div>

Normally if you attempt to change a configuration that has been resolved you get an error message:

“You can’t change a configuration which is not in unresolved state”

However, in multi-project builds you can change a configuration defined in one project, after a down-stream project has already resolved it. This results in a confusing state where some projects see the old configuration and some see the new one.

I discovered this after spending a lot of time trying to debug why when I replaced my default artifact it wasn’t getting picked up by some downstream projects. See [http://forums.gradle.org/gradle/topics/how\_do\_you\_change\_the\_default\_artifact\_in\_a\_multi\_project\_build](http://forums.gradle.org/gradle/topics/how_do_you_change_the_default_artifact_in_a_multi_project_build)