Return-Path: 
 <derby-dev-return-75890-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 391 invoked from network); 11 Feb 2010 21:26:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 11 Feb 2010 21:26:49 -0000
Received: (qmail 29205 invoked by uid 500); 11 Feb 2010 21:26:49 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 29174 invoked by uid 500); 11 Feb 2010 21:26:49 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 29146 invoked by uid 99); 11 Feb 2010 21:26:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Feb 2010 21:26:49 +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, 11 Feb 2010 21:26:48 +0000
Received: from brutus.apache.org (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 4495B29A0014
	for <derby-dev@db.apache.org>; Thu, 11 Feb 2010 13:26:28 -0800 (PST)
Message-ID: <632871227.215341265923588279.JavaMail.jira@brutus.apache.org>
Date: Thu, 11 Feb 2010 21:26:28 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4548) would like an alternative location
 for ant.properties
In-Reply-To: <594392802.215271265922508638.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/DERBY-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832686#action_12832686 ] 

Kristian Waagan commented on DERBY-4548:
----------------------------------------

Just so I don't misunderstand, is this something you cannot do with the ant -propertyfile command line option?
Or do you want to change this "once and for all" for a given checked out source tree?
And if you need to do it per tree, does it work to simply edit the one line above in build.xml?

> would like an alternative location for ant.properties
> -----------------------------------------------------
>
>                 Key: DERBY-4548
>                 URL: https://issues.apache.org/jira/browse/DERBY-4548
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.0.2.2, 10.1.3.3, 10.2.2.1, 10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.0.0
>            Reporter: Myrna van Lunteren
>
> The current build.xml directs ant to look for a file ant.properties in user.home. 
> This can get confusing when you have multiple versions on the same machine.
> I've worked around this in the past by pointing ant at other directories with -Duser.home=..., but it would be easier to have another place set up - I don't really like changing user.home.
> We could add another line to build.xml, e.g., for trunk's current build.xml:
> @@ -20,6 +20,7 @@
>  <!-- Set Properties -->
>    <!-- User settings -->
> +  <property file="ant.properties"/>
>    <property file="${user.home}/ant.properties"/>
>    <!-- Set property lib dir -->
>    <property name="properties.dir" value="tools/ant/properties"/>
> This would make ant look first for ant.properties in the same directory as the top level build.xml, and secondly for the one in user.home.
> If the community agrees this would be ok, I'd like to make this change and backport it all the way to 10.0.
> By having an additional place we'd not cause incompatibilities to other build processes (except if someone has put an ant.properties file in the top of the checked out tree).
> If we do this, I think it's up to the developers to ensure that there's not 2 ant.properties files that are conflicting. 

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