I started to try to scoping for the ivy :settings with the same idea than Maarten (<ivy:settings id="my-settings" settings="settings.xml" /> <ivy:resolve resolveId="my-resolve" settingsRef="my-settings" /> <ivy:cachepath resolveId="my-resolve" settingsRef="my-settings" />)
And during the test I notice a side effect that I didnt expected. The trace of the old configure task are now present in the first task to use the settings (of curse, you would say). For the settings, it is not really an issue. However, if we go up to the ivy:cachepath datatype, it might be more problematic. We could end with all the resolve traces under a [java] task, which might be disappointing for the user. We should probably see it in action before really evaluate the impact, but that's a potential issue. What is your feeling about that? Gilles
