[
https://issues.apache.org/jira/browse/DERBY-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-4575:
---------------------------------
Description:
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.
was:
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.
> 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.
