Hey,
Currently, we don't detect a change to the configuration after it was
resolved, when the change happens within hierarchy. For example:
configurations {
foo
bar.extendsFrom foo
}
configurations.bar.resolve()
//add dependency to bar, via configuration hierarchy:
dependencies { foo "org.lib:1.0" }
Is this by design? I just came across a hard-to-debug problem related
to this. I would prefer if this scenario was better handled, perhaps
even by preventing the dependency addition. However, I may not see the
full picture.
Sometimes I wish that an explicit "resolve()" was required to get the
configuration resolved. Sometimes it's easy to trigger resolution
without even knowing.
Cheers!
--
Szczepan Faber
Core dev@gradle; Founder@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
