Hi, It seems to work alright based on my test case. As per Erik's suggestion, I reviewed the "prefix" parameter of the property task:
"Prefix to apply to properties loaded using file or resource. A "." is appended to the prefix if not specified." I wasn't able to extrapolate from that description how that could be applied to what I'm up to, unless the idea is that I could prefix one set of properties to be sure they didn't collide with the other set? Since each file contains it's own unique set of properties and values, I'm not sure I would need to go down that path...? Matt -----Original Message----- From: Matt Benson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 4:53 PM To: Ant Users List Subject: Re: property file Sounds fine to me... -Matt --- Matt Lyon <[EMAIL PROTECTED]> wrote: > Hi, > > Is there any problem with loading two separate > property files during a build if they are defined at > a global scope in the build file and contain values > that are totally unrelated? I have one file, > 'build.properties' that contains compiler settings > and so forth, and another, 'bom.properties' that > contains named value pairs of modules from our cvs > repository and corresponding tags for each module. > Ideally, I would like to keep the property values > separated out into two files and load them both. > > Matt > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
