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] Updated: (DERBY-4548) would like an alternative location for ant.properties
Date Tue, 16 Feb 2010 19:03:27 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-4548:
--------------------------------------

    Issue & fix info: [Patch Available]

I intend to commit this and backport tomorrow if there are no further comments/objections...

> 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: 10.0.2.2, 10.1.3.3, 10.2.2.1, 10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.0.0
>            Reporter: Myrna van Lunteren
>         Attachments: DERBY-4548.diff
>
>
> 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.


Mime
View raw message