Hi All, The Maven documentation is looking great! I have read the section on Best Practices (http://maven.apache.org/using/bestpractices.html) and have a question regarding generating deployments. One bullet point states the following:
"Avoid the need to filter resources. While this can be useful in a development environment, it usually requires rebuilding of an artifact between different phases of deployment. The best alternative is to externalise the configuration - for example in J2EE (where this is a common occurrence), make sure all configurable information such as database connection properties are in the deployment descriptor, provided through JNDI outside of the webapp or other deployable item. This means the particular artifact can be deployed identically into different servers, with just the external configuration differing." Can somebody elaborate on how to achieve this? I certainly would love to be able to do this, as this is one of the pain points I have on my projects. Currently we have separate properties files containing settings for our separate deployment environments. When we build our webapps for deployment, we specify the target environment so that we filter resources with the corresponding properties file. This ensures that the configuration files deployed with the application contain the settings appropriate for the target environment. How can we use the best practice quoted above to avoid this? What do others do to address this issue? Thanks, Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
