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]
