[jira] Commented: (DERBY-4575) Provide an ant property that would make the build disregard ant.properties and local.properties

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

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

> I thought that the values specified in local.properties override
> those in ant.properties. At least, that's the way that I read Myrna's
> last comment in DERBY-4548. 

That's my understanding too. I was thinking about the opposite case,
that not setting a property in local.property is not enough to ensure
that the default value is used if you have ant.properties.

If you want to write a local.properties that ensures that the result
of the build is completely independent of what you have in
ant.properties, you need to specify each and every property used in
the build scripts, even if you want to use the default value for most
of them. With a property to disable ant.properties, you only need to
specify those you want to have a non-default value.

> Provide an ant property that would make the build disregard ant.properties and local.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/local.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.