db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4548) would like an alternative location for ant.properties
Date Fri, 12 Feb 2010 00:46:27 GMT

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

Myrna van Lunteren commented on DERBY-4548:

For an example, I want to prevent that making changes for tinkering for a bug in trunk, affects
my settings for building 10.5 - so that I can immediately build my 10.5 when I need...Or,
for building 10.2, I need to use wctme5.7's libraries, but for 10.5 I want to use weme6.2
If I make a modification to the build.xml, and build like that, the version output from sysinfo
gets the funky M attached, which I don't want. And I don't want to risk inadvertently checking
in such a change.

The main reason for not liking -Dpropertyfile is that I don't want to have to type something
extra (or even have an alias). 

Another note re precedence for the case when there's multiple 'matching' property files -
the properties don't seem to be incremental. For instance, when providing no proceed setting
in user.home/ant.properties but proceed=true in the propertyfile passed in with -Dpropertyfile,
the output from ant shows that Proceed=no. 
My testing shows that the file listed in build.xml gets precedence, and whichever file is
listed first in build.xml gets precedence. 

Would it be acceptable to have the local ant.properties first?

> would like an alternative location for ant.properties
> -----------------------------------------------------
>                 Key: DERBY-4548
>                 URL: https://issues.apache.org/jira/browse/DERBY-4548
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:,,,,,,
>            Reporter: Myrna van Lunteren
> The current build.xml directs ant to look for a file ant.properties in user.home. 
> This can get confusing when you have multiple versions on the same machine.
> I've worked around this in the past by pointing ant at other directories with -Duser.home=...,
but it would be easier to have another place set up - I don't really like changing user.home.
> We could add another line to build.xml, e.g., for trunk's current build.xml:
> @@ -20,6 +20,7 @@
>  <!-- Set Properties -->
>    <!-- User settings -->
> +  <property file="ant.properties"/>
>    <property file="${user.home}/ant.properties"/>
>    <!-- Set property lib dir -->
>    <property name="properties.dir" value="tools/ant/properties"/>
> This would make ant look first for ant.properties in the same directory as the top level
build.xml, and secondly for the one in user.home.
> If the community agrees this would be ok, I'd like to make this change and backport it
all the way to 10.0.
> By having an additional place we'd not cause incompatibilities to other build processes
(except if someone has put an ant.properties file in the top of the checked out tree).
> If we do this, I think it's up to the developers to ensure that there's not 2 ant.properties
files that are conflicting. 

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

View raw message