[ http://jira.codehaus.org/browse/MNG-416?page=all ]
John Casey updated MNG-416:
---------------------------
Fix Version: 2.2
this looks more like some sort of tool development than simply writing a
document to indicate a "best practice" that effectively endorses one of these
solutions...
Assuming we want to write a config tool like this, would Maven really be a good
home for it? It'd be more of a runtime tool, rather than a development tool...
Assuming we don't want to write a tool, is it really appropriate for us to
endorse another tool over the rest? Is there a clear winner in the problem
space right now, under all circumstances?
> best practices: multiple profile deployments
> ---------------------------------------------
>
> Key: MNG-416
> URL: http://jira.codehaus.org/browse/MNG-416
> Project: Maven 2
> Type: Task
> Components: Design, Patterns & Best Practices
> Reporter: Brett Porter
> Priority: Trivial
> Fix For: 2.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
