On 2015-09-03 11:04, Matthieu Baechler wrote:
Hi Eric,
On 03/09/2015 10:16, Eric Charles wrote:
I like Matthieu proposal (merge without mime4...), but this will open
the door to more refactoring that would maybe go against the initial
requirement of being able to embed some mailbox without the full server.
Of course, as the mailbox API will probably change more often, it will
break potential mailbox-api direct users. It leads to two questions :
- is there such users ?
- do we expect alpha/beta software to be API stable ?
I really like the idea of merging things until 3.0 release happens then
decide if we split back or not.
If we merge, we should be sure this is the right thing to do before and
after 3.0.
Why would we split again after 3.0?
Maybe we should write to guidelines we can refer when working in that
single repository, otherwise we will have endless discussions that don't
occur for now simply because code live in separate projects.
I think maven dependencies capture the intent of module responsibility
very well. What would you want the guidelines to contain ? API stability
rules ? Anything else ?
Classes, Packages, Maven submodules and repositories all serve IMHO
segregation of responsibility and API.
For now, we have hard barrier that prevent someone to break this.
I was thinking more about a documented diagram such as the one I started
on http://james.apache.org/server/3/dev.html to show the modules
interactions and boundaries.
A common understanding of such a representation will ease later discussion.
API stability is another concern to be addressed once we have the
architecture documented.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
