You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2006/01/06 02:17:10 UTC
[jira] Updated: (MNG-416) best practices: multiple profile
deployments
[ http://jira.codehaus.org/browse/MNG-416?page=all ]
Jason van Zyl updated MNG-416:
------------------------------
Component: (was: documentation - best practices)
design
> best practices: multiple profile deployments
> ---------------------------------------------
>
> Key: MNG-416
> URL: http://jira.codehaus.org/browse/MNG-416
> Project: Maven 2
> Type: Task
> Components: design
> Reporter: Brett Porter
> Fix For: 2.0.3
>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org