Affects Version/s: None
Fix Version/s: None
It should be mentioned clearly the sequence happening to resolve properties.
An ivy.instance reference might exists already due to a prior call to <resolve/> which may then make it available to tasks such as <publish/>.
If you forget to make target dependencies between <publish/> and <resolve/> you end up with a cryptic message about missing properties/attributes/...
It is not especially striking that the order of properties is:
1) task attribute
2) ivy instance
3) project property
The existing ivy instance (or not) is particulary vicious.
I'm also thnking it may make sense to use debug messages to say which property is picked from where.
Ivy is not giving much info, so debugging build issues requires to fire a debugger which is not exactly user friendly.