[
https://jira.codehaus.org/browse/MNG-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-416:
------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> best practices: multiple profile deployments
> ---------------------------------------------
>
> Key: MNG-416
> URL: https://jira.codehaus.org/browse/MNG-416
> Project: Maven
> Issue Type: Task
> Components: Design, Patterns & Best Practices
> Reporter: Brett Porter
> Priority: Trivial
>
> There have been several threads on the user and dev list following on from
> the recommendations made in the best practices document.
> The objective is to make an artifact standalone, without the need to rebuild
> to deploy to a new environment. Configuration should be externalised (or all
> stored inside and selected based on an externalised parameter). This can
> usually be done with JNDI in J2EE (especially for database configurations),
> but this has a couple of limitations:
> - JNDI can be awkward and may not be available outside of the container
> (though directory-naming can be used)
> - some things in the deployment descriptor must be inside the artifact, but
> need to be different between environments (eg security settings in web.xml
> and a bunch of weblogic specific files for which the container does not
> provide external/admin based configuration for).
> Some products to consider:
> - payload/genesis: http://www.osjava.org/payload/
> - easyconf: http://easyconf.sourceforge.net/index.html
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
