[JAMES-3259] Reorganize source code

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.5.0
• Assignee: Unassigned
• Reporter: Matthieu Baechler
• Created: 19/Jun/20 07:28
• Updated: 06/Jul/20 07:40

Description

I want to suggest a new organization of the source-code (I won't handle every concerns but some important ones I have about the current state).

I would like the first level to be:

core (domain code)
data (that we should rename)
docs
extensions (containing mdn and third-party for example)
infrastructure (containing backends-common, event-sourcing, json, metrics)
mailbox
mailet
products (containing server/container/cli server/container/guice/cassandra-rabbitmq-guice)
protocols
server
testing (containing mpt)

I'm not sure it's the best organization but:

• it allows to see easily what james most important concepts are
• put technical details into a common sub-tree
• have products a top level thing instead of a hidden one
• group what we think are extensions somewhere
• put functional testing sources somewhere that is easy to find (because a lot of people starts by reading functional tests)

What do you think?

Issue Links

• is related to: JAMES-2510 use a consistent artifact naming scheme

Sub-Tasks

• [Experiment] Re-write the SMTP API: Closed