>I agree that putting <filtering> in the POM is a good first approach but >that it won't handle the need for different environments. > >This is something that I've been wanted to include in maven for a very long >time: the ability to say "build me this project for this environment". > > > > As I said, I'm stil not convinced this is a good way to go. - unless you have a clear way to identify, it's hard to tell what env it belongs to - its rarely a good idea to rebuild for a move through the final testing phases as you want to change as little as possible
I'm more in favour of us lending a hand with configuration management that is external to the artifacts, and using the filtering to populate some variables from a central location, and ease development. >It seems that you're currently moving in the direction of doing this with >the settings.xml file. However I'm concerned that the definition of the >different environments is something that you need to share with your >co-workers so it can't be located in a file that contains machine-dependent >information such as (location of your local repo, etc). In other words parts >of the environment definition should be shared through the SCM and part >shouldn't. > > > > I don't think we want to put anything in settings.xml that is shared - what is in there are passwords and passhphrases and paths. The common things - repository url, etc are in pom.xml. What are you thinking is going into settings.xml that is shared? - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
