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 "Norman Maurer (JIRA)" <se...@james.apache.org> on 2011/06/29 22:28:28 UTC
[jira] [Resolved] (JAMES-1284) Merge mailetcontainer-library and
mailetcontainer-camel
[ https://issues.apache.org/jira/browse/JAMES-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-1284.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta1
Assignee: Norman Maurer
done
> Merge mailetcontainer-library and mailetcontainer-camel
> -------------------------------------------------------
>
> Key: JAMES-1284
> URL: https://issues.apache.org/jira/browse/JAMES-1284
> Project: JAMES Server
> Issue Type: Task
> Components: SpoolManager & Processors
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 3.0-beta1
>
>
> After thinking a bit more about the whole mailetcontainer-* modules I came to the conclusion that we should better merge mailetcontainer-library and mailetcontainer-camel. I think Stefano proposed exactly this before. I was against this change in the past but I think I now see the benefits.
> At the moment we have mailetcontainer-library and mailetcontainer-camel which both use the same configuration file (mailetcontainer.xml). This is not really good as we need to ship the config file in both "bundles/modules".
> I know the mailetcontainer-library has classes which don't depend on camel but as Stefano told before we can still split it later if we really need to..
--
This message is automatically generated by JIRA.
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