Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0
-
None
-
None
Description
When using more the one ivysettings.xml-s inside the same user account (same computer), the result is often a lot of "unknown resolver" errors, and other such mess. The cause is that caches were not set up properly: I guess usually there should be one repository cache per ivysettings.xml, then one dedicated resolution cache per ivysettings.xml too (at least, because if parallel builds use a common ivysettings.xml, then each of them needs its own). These I mostly deduced from mailing list discussions and experimenting, not from the documentation. So, these things should be well described, and then linked from every place that's about wiring ivysettings.xml-s. (Even maybe the "unknown resolver" error messages could contain a hint about what the problem could be.) Also, the users should be warned about the importance of lock strategies. (I know that in principle these could be find out from http://ant.apache.org/ivy/history/latest-release/concept.html#cache, but that description is at best sparse, and the implications are not described. Also it's not on a very well visible place.)