Robert Burrell Donkin ha scritto:
there's a lot of code in IMAP-Mailbox. this creates a large barrier to
entry both for developers wanting to work on IMAP-Maibox and for
developers who want to work on other components.
i'd like to think about moving the whole of the IMAP-mailbox code base
out of server/trunk and into server/protocols/imap/trunk (say). this
move would include the sieve mailet.
-0. I don't think that disgregation of code will help: we already moved
mailet outside from james server. We made james server modular. I want
to see some releases before any other disgregation is done. I'd like to
see proofs that this road works for real before following it so much.
Releases should be the goal, and in the last year we only had 2 jSPF
releases and nothing else :-((
Is IMAP-mailbox a standalone library? Has it any use separated from
JAMES Server code? Is there any developer working on that code lamenting
the issue of having to work with the whole "server" checked out?
Furhermore at "server" level we already have the TTB structure
(trunk/tags/branches), I will probably -1 adding a "protocol" folder at
the same level. IMHO it is against the least surprise principle.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
