You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Matthieu Baechler (Jira)" <se...@james.apache.org> on 2020/06/19 07:29:00 UTC

[jira] [Created] (JAMES-3259) Reorganize source code

Matthieu Baechler created JAMES-3259:
----------------------------------------

             Summary: Reorganize source code
                 Key: JAMES-3259
                 URL: https://issues.apache.org/jira/browse/JAMES-3259
             Project: James Server
          Issue Type: Improvement
    Affects Versions: 3.5.0
            Reporter: Matthieu Baechler


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:

{code}
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)
{code}

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?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org