Create a message module and maybe an encoder/decoder module.
------------------------------------------------------------
Key: IMAP-56
URL: https://issues.apache.org/jira/browse/IMAP-56
Project: JAMES Imap
Issue Type: Task
Components: Build System
Reporter: Stefano Bagnara
Assignee: Stefano Bagnara
Priority: Minor
Fix For: 0.1
I see some module is really small (seda) while other modules are really big
(codec). I graphed the package dependency tree (it is a tree only after
grouping the 2 cycles above) and it resulted that the codec module have 2
separated hierarchies:
http://people.apache.org/~bago/imap/graph-imap-full-package-check-no-torque.gif
Does it worth splitting? (note that imap.message.request.base+imap4rev1 and
imap.command.imap4rev1 can be moved in both "groups").
3b) maybe we could even shorten package names: codec.encode => encode and
codec.decode => decode
3c) another option would be to extract the imap.message package to its own
module (message). codec (or both decode/encode if it is splitted) would then
depend on this message module). If I'm not wrong processor would so depend only
on "message" and not on codec(decode/encode).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
