You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Eric Charles (Created) (JIRA)" <se...@james.apache.org> on 2012/02/16 12:27:00 UTC
[jira] [Created] (JAMES-1376) Config should belong to their
modules, shipping should only contain templates
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
[jira] [Commented] (JAMES-1376) Config should belong to their
modules, shipping should only contain templates
Posted by "Ioan Eugen Stan (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210224#comment-13210224 ]
Ioan Eugen Stan commented on JAMES-1376:
----------------------------------------
First I would like to correct a mistake about conffiles: Debian Policy requires that they are specified in a special file inside the deb-archive called conffile. They do not have to end in conf, so that should be up to us. Files that end in conf are more suggestive to me.
I also agree with the fact that stuff that james users/admins should not modify should be embedded in jars. I'm not sure about database.properties though, from what I know, you specify the db connection url there.
My general thought on this is that we should export to the users as little configs as possible, with sane defaults.
> 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
[jira] [Commented] (JAMES-1376) Config should belong to their
modules, shipping should only contain templates
Posted by "Ioan Eugen Stan (Commented) (JIRA)" <se...@james.apache.org>.
[ 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
[jira] [Commented] (JAMES-1376) Config should belong to their
modules, shipping should only contain templates
Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210149#comment-13210149 ]
Eric Charles commented on JAMES-1376:
-------------------------------------
Yes, the maven debian profile can do some more work, such as moving and renaming the template files.
We can rename the current *.xml configuration files to *.conf, that will make things more obvious.
Upon the *.xml files, there are also a few properties (jmx.properties, database.properties) to deal with, and also the spring context definitions (xml) which are now in META-INF/org/apache/james and embedded in jars. These are more system-wide definitions, and not configuration. In my sense, it should not be accessible to a end-user, even not to a mail server administrator.
> 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
[jira] [Closed] (JAMES-1376) Config should belong to their modules,
shipping should only contain templates
Posted by "Eric Charles (Closed) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Charles closed JAMES-1376.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta4
Assignee: Eric Charles
Done. Can be closed.
> 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
> Assignee: Eric Charles
> Fix For: 3.0-beta4
>
>
> 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
[jira] [Commented] (JAMES-1376) Config should belong to their
modules, shipping should only contain templates
Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210246#comment-13210246 ]
Eric Charles commented on JAMES-1376:
-------------------------------------
Let's favor *.conf for all end-user configuration stuff that are not properties.
database.properties now reside in /META-INF/org/..., but we could move it to / , so it can be considered also as end-user configuration, such as log4j.properties and jmx.properties.
I will commit something around this weekend.
> 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