Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-3259

Reorganize source code

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.5.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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?

        Attachments

        Issue Links

        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              matthieu Matthieu Baechler

              Dates

              • Created:
                Updated:

                Issue deployment