james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioan Eugen Stan (Commented) (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1376) Config should belong to their modules, shipping should only contain templates
Date Thu, 16 Feb 2012 22:10:59 GMT

    [ https://issues.apache.org/jira/browse/JAMES-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209795#comment-13209795
] 

Ioan Eugen Stan commented on JAMES-1376:
----------------------------------------

It could work in the sense that we can we can supply properties specific for deb generation
(specific paths and names) and use maven resource filters to replace those properties. If
I misunderstood please elaborate, but I think it's ok to have the config with the package
for the reasons you mentioned. I hope this will make hot configuration reloading more accessible
to develop since things will be more clear as to how the configs are spread. 

About config files in Debian, the policy mandates that either they end in '.conf' and are
in /etc/xx or otherwise are created at install  time (or later) in /etc/xx. I will write some
post-install scripts to symlink the conf files from /usr/share/james/conf to /etc/james. We
should provide sensible defaults as basic install config files. 
                
> 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