[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [stellation-res] Windows Port
|
At 06:22 PM 5/14/2003, Jonathan Gossage wrote:
Se embedded comments
> -----Original Message-----
> From: stellation-res-admin@xxxxxxxxxxxxxxx
> [mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Jim Wright -
> IBM Research
> Sent: Wednesday, May 14, 2003 2:50 PM
> To: stellation-res@xxxxxxxxxxxxxxx
> Subject: [stellation-res] Windows Port
>
>
> Jonathan,
>
> Back on May 1, I posted an attachment to your Bugzilla #35267
> "Windows Port Patch", with some revised scripts and other files.
> In a followup message (same day), I posed a question about
> whether the scripts should attempt to handle multiple database
> types in a single run (which complicates things significantly),
> rather than using a separate properties file to select a particular
> database.
The biggest problem I have is that I don't like systems that rely on manual
copying. It is too error-prone. Perhaps we could define a database selector
property to be entered on the command line that would result in the
selection of an appropriately named properties file. If you agree with this
suggestion I will update the stuff you sent to do this
That would work; something like this:
ant -Ddb.selector=DB_SELECTOR_PATH
where DB_SELECTOR_PATH is
{firebird.local,firebird.remote,postgres.local,postgres.remote...}
Then, the Ant scripts would use something like this:
<property name="local.propertyfile"
value="${user.home}/stellation/${db.selector}/stellation.XXX.properties"
/>
where XXX = {build,test}.
If db.selector is not defined, the script should fail with an appropriate
message.
If db.selector _is_ defined but the stellation.XXX.properties file is not found
in the specified location, the script should do what it does now:
* copy a default file into the specified location (creating it if necessary)
* exit with message requesting the user to edit the copied file.
This avoids manual copying, makes it simple to configure the db-specific
property files,
and keeps the Ant scripts from getting too complicated.
Works for me ---- or maybe just name the files ${db.selector}.test.properties,
${db.selector}.build.properties etc. and keep them all in
${user.home}/stellation.
Whichever you prefer is fine by me.
Thanks,
Jim
--------------------------------------------------------------------
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
jim.wright@xxxxxxx
