Thank you Ondřej > This tutorial should give you all information you need: > > http://www.manydesigns.com/documentation/tutorials/using-maven-profiles-and-resource-filtering.html
That's a bit better than what I'm currently doing (which is using profiles, but keeping multiple copies instead of using resource filtering). However, what my Configuration Manager wants is to have the build result in a single war and deploy the configuration files separately. For him, the result of the build should be Project.war, Project-DEV.tar, Project-QA.tar, Project-PROD.jar I'm not convinced this is the best approach. Is the consensus that the method described in that tutorial is "correct"? I believe there is some argument against having <profile> in Maven (from Stephen Connelly?) So maybe there are some non-profile ways to accomplish this. Would the Maven Way still be to execute separate builds per environment? -- Greg Akins http://twitter.com/akinsgre --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
