Return-Path: 
 <notifications-return-8246-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 2830 invoked from network); 14 May 2009 19:01:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 14 May 2009 19:01:08 -0000
Received: (qmail 77272 invoked by uid 500); 14 May 2009 19:01:08 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 77246 invoked by uid 500); 14 May 2009 19:01:08 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 77237 invoked by uid 99); 14 May 2009 19:01:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 19:01:08 +0000
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, 14 May 2009 19:01:06 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 3AB11234C004
	for <notifications@ant.apache.org>; Thu, 14 May 2009 12:00:46 -0700 (PDT)
Message-ID: <1163232234.1242327646228.JavaMail.jira@brutus>
Date: Thu, 14 May 2009 12:00:46 -0700 (PDT)
From: "Jeff Glatz (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Created: (IVY-1074) Provide a 'required' attribute to ivy
 settings/properties element to control reaction to missing properties file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org

Provide a 'required' attribute to ivy settings/properties element to control reaction to missing properties file
----------------------------------------------------------------------------------------------------------------

                 Key: IVY-1074
                 URL: https://issues.apache.org/jira/browse/IVY-1074
             Project: Ivy
          Issue Type: Improvement
          Components: Core
            Reporter: Jeff Glatz
            Priority: Critical


we use ivy in our company and have our repository under version control which is checked out alongside our projects. our setup is designed to work when run from builds on an integration server, on developer's machines, and from under IDE plugins for IDEA and eclipse.

because the repository checkout will vary based on environment, we expect that a property called 'libraries.root' is defined and points to the individual repository location. when run from ant, this value is provided as a build property. the issue arises when ivy is run from the plugins because 'libraries.root' is never set.

to facilitate this, we use a single ivysettings.xml file which does the following:

{code:xml|title=ivysettings.xml}
<ivysettings>
   ...
   <properties file="${ivy.settings.dir}/${user.name}.properties"/>
   ...
</ivysettings>
{code}

to load a properties file for the user where 'libraries.root' is defined.

the problem is that there are cases, such as when run under the integration server, where the user will not have a properties file. in this case, the configuration blows up. i propose adding a 'required' attribute to control the reaction to a missing file:

{code:xml|title=ivysettings.xml}
<ivysettings>
   ...
   <properties file="${ivy.settings.dir}/${user.name}.properties" required="false"/>
   ...
</ivysettings>
{code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.