And in response to Martin, in the project I'm recently involved in, the paths are not hard-coded into the build script itself but rather in various build.properties files. It is still a total pain and a hack, IMO. You can't honestly tell me that you enjoy configuring properties files for every environment/machine, do you? I have better things to do with my time.
After a lot of time with Maven over the last few years, it will be a cold day in hell when I go back to making Ant scripts. Instead, I'm fixing the mistakes of others and getting rid of their Ant scripts. Wayne On 3/28/08, Wayne Fay <[EMAIL PROTECTED]> wrote: > On 3/28/08, Graham Leggett <[EMAIL PROTECTED]> wrote: > > Hard coding paths is one of the exact things that was rife in ant builds > > and that maven moves away from, and that makes code management > > significantly less painful and more robust. > > I just got pulled into a project at my work place where they are > having significant build problems, and guess what, its Ant-city with > hard-coded paths like you wouldn't believe. For some reason, this > approach is starting to have problems now that more than 2 devs are > involved, and the project is getting ready to hit production for the > first time. > > Wayne > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
