>The only restriction would be where the Struts build.xml looked for
>build.properties. My proposal would be that it should be in the same
>directory that build.xml is (but, as mentioned earlier, *not* checked in
>to CVS). That way, you can have different sets of build properties for
>your different projects without having to continually modify environment
>variables.
I really like including a properties file from the current directory (in
relation to build.xml) as well as one from a centralized place (like the user's
home directory).
Essentially:
<property file="build.properties" />
<property file=${user.home}/build.properties" />
And of course these statements are ignored if the files don't exist.
>Essentially, "build.properties" replaces having to set all the environment
>variables required by the current "build.sh" and "build.bat" scripts, but
>gives you the same flexibility to use whichever components *you* want to,
>without impacting which ones *I* am using (and vice versa). Am I missing
>something?
>Craig
mark
Mark R Mascolino
The Procter & Gamble Co.
[EMAIL PROTECTED]
