>> <property file="build.properties" />
>> <property name="wolips.properties" value="wolips.properties" />
>> <property file="${user.home}${file.separator}Library${file.separator}Application Support${file.separator}WOLips${file.separator}${wolips.properties}" />
>>
>> FWIW, I have my own build scripts that I use for all of my apps. It is probably less Eclipse friendly, but seems more manageable from the command line.
>
> I think your little switcheroo there is *exactly* what the stock build.xml ought to look like, because now, you can just add (for example):
> wolips.properties=wolips.533.properties
> to your build.properties, and it works for both the internal builder and for Ant. Eclipse will treat it as being relative to ~/Library/Application Support/WOLips/, and so does the Ant script.
The problem is that the full implementation of loading props isn't quite that simple ... This probably really has to be a WOLipsProperties ant task that calls the same code that WOLips uses to locate the properties file to work correctly. If you're on the Mac and you're using the standard location, then this will probably work for you.
ms
This archive was generated by hypermail 2.0.0 : Thu Feb 18 2010 - 10:11:31 EST