[ http://jira.codehaus.org/browse/MNG-416?page=all ]
John Casey updated MNG-416:
---------------------------
Fix Version: (was: 2.0.1)
2.0.2
> best practices: multiple profile deployments
> ---------------------------------------------
>
> Key: MNG-416
> URL: http://jira.codehaus.org/browse/MNG-416
> Project: Maven 2
> Type: Task
> Components: documentation - best practices
> Reporter: Brett Porter
> Fix For: 2.0.2
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
