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. initially, trunk would then depend on SNAPSHOT jars committed into the stage directory for IMAP support. in the medium term, i'd like to move towards lightweight embeddable protocol libraries but i think it would be better if that were discussed in a separate email. opinions? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
