db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4575) Provide an ant property that would make the build disregard ant.properties
Date Thu, 04 Mar 2010 16:09:27 GMT

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

Dag H. Wanvik commented on DERBY-4575:

I think what I want here is the ability to make sure that no contextual (other than command
line) properties are being picked up. For example, if a Derby build is part of larger build,
I would not want the person building to worry about having property files lying around. A
bit like "env - name=<value> <command>" in the shell...

> 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=...
> 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.

View raw message