[
https://issues.apache.org/jira/browse/JSIEVE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212835#comment-13212835
]
Eric Charles commented on JSIEVE-86:
------------------------------------
I think steve was seeing this as a separate library independent of jsieve and
server. This can make sense, but for practical reasons (release,
maintenance,...) I see it more withing sieve. Now, if the dependency on server
file-api makes it not possible. The "ultimate" solution to me would be to
extract the classes common to different projects to a james-common library, but
I already told you were not in favor of it. The integration of managesieve in
server would make things easier for now, for sure.
> 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
