james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Charles (Created) (JIRA)" <server-...@james.apache.org>
Subject [jira] [Created] (JAMES-1376) Config should belong to their modules, shipping should only contain templates
Date Thu, 16 Feb 2012 11:27:00 GMT
Config should belong to their modules, shipping should only contain templates
-----------------------------------------------------------------------------

                 Key: JAMES-1376
                 URL: https://issues.apache.org/jira/browse/JAMES-1376
             Project: JAMES Server
          Issue Type: Improvement
            Reporter: Eric Charles


Now that JAMES-1002 is completed, we can look at further OSGI working and also configuration
shipping.

The proposal is:
- Move the default configuration to their own module (smtpserver.xml to smtp module...)
- Have some templates (smtp.xml.template ) shipped so a administrator can override the smtp.xml
with the provided template. We should use the files https://svn.apache.org/repos/asf/james/app/trunk/src/main/config/examples.
This has a benefits that these rich configured files will be used and reviewed along the recent
changes.

@Ioan, I wonder if the *.xml.template would work with JAMES-1343?


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message