From notifications-return-7715-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org Thu Mar 12 23:03:14 2009 Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 68994 invoked from network); 12 Mar 2009 23:03:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2009 23:03:13 -0000 Received: (qmail 39896 invoked by uid 500); 12 Mar 2009 23:03:13 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 39866 invoked by uid 500); 12 Mar 2009 23:03:13 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 39857 invoked by uid 99); 12 Mar 2009 23:03:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 16:03:13 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 23:03:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 86F14234C046 for ; Thu, 12 Mar 2009 16:02:50 -0700 (PDT) Message-ID: <2014433212.1236898970551.JavaMail.jira@brutus> Date: Thu, 12 Mar 2009 16:02:50 -0700 (PDT) From: "Daniel Dekany (JIRA)" To: notifications@ant.apache.org Subject: [jira] Created: (IVY-1049) Describe how to setup the caches, especailly for multiple ivysettings.xml-s MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Describe how to setup the caches, especailly for multiple ivysettings.xml-s --------------------------------------------------------------------------- Key: IVY-1049 URL: https://issues.apache.org/jira/browse/IVY-1049 Project: Ivy Issue Type: Improvement Components: Documentation Affects Versions: 2.0 Reporter: Daniel Dekany When using more the one ivysettings.xml-s inside the same user account (sam= e computer), the result is often a lot of "unknown resolver" errors, and ot= her such mess. The cause is that caches were not set up properly: I guess u= sually there should be one repository cache per ivysettings.xml, then one d= edicated resolution cache per ivysettings.xml too (at least, because if par= allel builds use a common ivysettings.xml, then each of them needs its own)= . These I mostly deduced from mailing list discussions and experimenting, n= ot from the documentation. So, these things should be well described, and t= hen linked from every place that's about wiring ivysettings.xml-s. (Even ma= ybe the "unknown resolver" error messages could contain a hint about what t= he 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 t= hat description is at best sparse, and the implications are not described. = Also it's not on a very well visible place.) --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.