[
https://issues.apache.org/jira/browse/JSIEVE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212684#comment-13212684
]
Stefano Bagnara commented on JSIEVE-86:
---------------------------------------
like we do with "Protocols", the "manager" should not have dependencies on
james server classes/api but use only "internal things". Then server can add
its own bridge. This separation of concerns force us to create a jsieve product
usable also by other developers not using james server.
If, instead, manager is way too specific to james server to be used by jsieve
users, then we should host it as a module in server and not in jsieve.
> Potential bidirectional dependency between jsieve manager and server
> --------------------------------------------------------------------
>
> Key: JSIEVE-86
> URL: https://issues.apache.org/jira/browse/JSIEVE-86
> Project: JAMES jSieve
> Issue Type: New Feature
> Reporter: Eric Charles
>
> sieve manager is aimed to be used in server
> james-server-filesystem-api is the one to talk about...
--
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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
