Put the properties themselves inside the profiles. Or, use filtering with various named filters eg qa.filter and specify the proper filter to use in your profile.
Wayne On 2/1/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote: > Hi all, > I know it is a well known issue but I am really stuck! > I am in the process of migrating some Java applications build system to > Maven 2. developers need to build the applications for different environment > like local/staging/QA/prod. in the old build system we have one property > file including all the environment related properties and we used to pass it > to build and get the job done. > These parameters includes actual values for filtered variables as well as > paths and plug in properties (ie. webapps.root for cargo plugin) > I created different profiles for different environment and everything was > going on well until I noticed that I can not load the property files inside > maven. Each profile needs to load one of the environment specific property > files; so that the rest of the maven could use it. > could somebody shed a light on this problem and guide me to load my property > file in maven, or tell me about any other solution. > > regards, > Arash > > -- > You can not depend on your eyes when your imagination is out of focus. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
