[EMAIL PROTECTED] writes: > Wouldn't it be easier to encapsulate those 6 different environments into > goals to set them up and process them?
I don't think so. You'd end up creating six new goals for each project, wouldn't you? And that would motivate you to encapsulate them in a plugin shared by each project. But the properties wouldn't be exactly the same for each project, so you'd customize the plugin with a properties file for each environment, and hey we're right back where we started. :-) I haven't thought it completely through, but wouldn't it be easier to introduce a mechanism by which additional properties files can be loaded; their precedence higher than project.properties but lower than [~/]build.properties? It might also be nice to have a goal for which I can specify pre/post conditions that determine which properties are loaded. Jim > "Nelson, Scott (MAN-Corporate)" <[EMAIL PROTECTED]> wrote on 26/11/2003 > 01:21:10 AM: > >> I need to manage builds to 6 different environments, instead of changing > the >> build.properties file every time before I run a build I thought it would > be >> easier to just specify a properties file to load with all the > environment >> specific settings for each separate environment. I was also thinking > once >> those property files are setup they could be managed in cvs. I guess > what I >> could do is have ant load the specified properties file in before any of > the >> plugins are called and not use maven's properties files at all for the >> environment deployment settings. Anyone else have another way to solve > this >> problem? >> >> -Scott >> >> --Original Message----- >> From: Jason van Zyl [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, November 25, 2003 12:15 AM >> To: Maven Users List >> Subject: Re: specify a different properties file rather than >> build.properties file >> >> >> On Mon, 2003-11-24 at 19:31, Nelson, Scott (MAN-Corporate) wrote: >> > Hey guys, >> > >> > After reading the documentation I know that the order of properties > file >> > processing is project.properties, build.properties, >> > build.properties(user.home). I also read that the -Dname=value > properties >> > set at the CLI take precedence over all of these but... >> > >> > Say I wanted maven to use a file called build-qa.properties instead of >> > build.properties, is there a way to do this in maven? >> >> Why would you need to that? >> >> >> -- >> jvz. >> >> Jason van Zyl >> [EMAIL PROTECTED] >> http://tambora.zenplex.org >> >> In short, man creates for himself a new religion of a rational >> and technical order to justify his work and to be justified in it. >> >> -- Jacques Ellul, The Technological Society >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Jim Crossley http://crossleys.org/~jim 404.409.9085 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
