You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2010/03/04 05:41:27 UTC
[jira] Created: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties
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.
[jira] Commented: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties
Posted by "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=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.
[jira] Updated: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties and local.properties
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties and local.properties
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841499#action_12841499 ]
Bryan Pendleton commented on DERBY-4575:
----------------------------------------
I understand more clearly the intent of this JIRA now. Thanks for the updated
description and clarifications. This seems like a useful feature to have.
> 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.
[jira] Commented: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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=... 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.
[jira] Updated: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties and local.properties
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-4575:
---------------------------------
Summary: Provide an ant property that would make the build disregard ant.properties and local.properties (was: Provide an ant property that would make the build disregard ant.properties)
> 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 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.
[jira] Commented: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841345#action_12841345 ]
Bryan Pendleton 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.
> 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.
[jira] Commented: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841315#action_12841315 ]
Bryan Pendleton commented on DERBY-4575:
----------------------------------------
Can the "local.properties" feature added by Myrna in DERBY-4548 be used for this?
> 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.
[jira] Commented: (DERBY-4575) Provide an ant property that would
make the build disregard ant.properties and local.properties
Posted by "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.