I think you can't deny MailAddress represent the same concept in both
mailet and protocols/smtp .
Thus, it seems logical to have one object to represent it.
I agree the way I proposed to share this code might not be optimal.
Maybe some common dependency might be better.
Note :
[
https://issues.apache.org/jira/browse/MAILBOX-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit resolved MAILBOX-267.
Resolution: Fixed
> Cassandra UID and ModSeq generation : build is unstable
>
[
https://issues.apache.org/jira/browse/MAILBOX-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed MAILBOX-267.
--
> Cassandra UID and ModSeq generation : build is unstable
>
[
https://issues.apache.org/jira/browse/JAMES-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laura Royet closed JAMES-1726.
--
Resolution: Fixed
merged
> setMailboxes : update can introduce duplicate
>
Repository: james-project
Updated Branches:
refs/heads/master 0395ee41b -> 16689d35e
JAMES-1726 Update can introduce duplicate
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/16689d35
Tree:
Antoine Duprat created JAMES-1732:
-
Summary: James init sequence should respect Dependency graph
Key: JAMES-1732
URL: https://issues.apache.org/jira/browse/JAMES-1732
Project: James Server
