Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <761752659.71671267717227260.JavaMail.jira@brutus.apache.org>
Date: Thu, 4 Mar 2010 15:40:27 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4575) Provide an ant property that would
 make the build disregard ant.properties
In-Reply-To: <146129316.57511267677687262.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen commented on DERBY-4575:
-------------------------------------------

I think you have the same problem with "local.properties", that you need to specify all properties to be sure that they are not overridden by ant.properties. If you had a property to disable ant.properties, you would only need to specify the properties that you wanted to give a non-default value in local.properties (or with -D on the command line).

> Provide an ant property that would make the build disregard ant.properties
> --------------------------------------------------------------------------
>
>                 Key: DERBY-4575
>                 URL: https://issues.apache.org/jira/browse/DERBY-4575
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>
> Sometimes it would be nice to build Derby in different contexts. The required settings in ant.properties sometimes differ when building different Derby versions, or when trying a new JDK, for example. It would be nice to have a property that one could set in the ant invocation to make it disregard the contents of ant.properties.
> E.g.
>      ant -Dpropertyfile=false -Dsane=false -Ddebug=false -Djava16compile.classpath=...  all
> Possibly, it could be useful for guaranteeing context correct for release builds as well.

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