[
https://issues.apache.org/jira/browse/JSIEVE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212975#comment-13212975
]
Stefano Bagnara commented on JSIEVE-86:
---------------------------------------
I didn't looked at manager previously, but I see manager is a multimodule
project and the only module depending on james-server is named "server" and is
a single class. So my suggestion is to keep everything in jsieve but the server
module and simply put the server module into the james-server trunk under a
sievemanager module (or something similar). Would this work? (otherwise I'm
fine with having all of it in james-server, too).
> 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
