On Tue, Jan 25, 2011 at 8:09 AM, Miguel Almeida <[email protected]> wrote: >> I agree with you. I'm still quite new to advanced Maven topics so it still > seems counter-intuitive to store the config file outside the .war - it adds > one extra step of "deploy the .xml/config file" in the installation, but > like Mark pointed out it makes the WAR more independent and more agile to > configuration changes.
If you had a finite number of configurations to support and you really wanted it all in a war, you could also organize your build as a base war module and then have the configurations in their own module and overlay them on top of the base war (google Maven war overlays). Profiles is the wrong tool for this job since there's no way you could release those properly. With an infinite number of configurations to support, the only right way is to externalize the configuration. Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
