Mark Hindess wrote:
> On 17 July 2006 at 15:34, Salikh Zakirov <[EMAIL PROTECTED]> wrote:
>>> Ivan Volosyuk wrote:
>>>> I have already implemented it using ant variables, look at the latest
>>>> patch. You can use following notation with it:
>>>> ant -Dhy.cfg=release
>> Geir Magnusson Jr wrote:
>>> Now we're getting somewhere.
>>>
>>> I assume then I can put this into the build.properties that we'll be
>>> adding Real Soon Now (as I can never remember command line args anyway...)
>> Please, please, do *not* introduce any more build.properties files.
>>
>> The files that may need to be customized to get specific build
>> configuration should never be version-controlled. Besides, keeping
>> configuration files in the workspace means you cannot make your
>> configuration permanent. I see the properties files as anti-usable.
>
> I'll let Geir speak for himself, but I think he was alluding to the use
> of a user properties file:
>
> <property file="${user.home}/.harmony.properties" />
>
> that would *not* be checked in and would be read (if it existed or
> ignored otherwise).
yes, but more than that - having configuration sets that could be
re-used is also a goal.
geir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
