On 2015-08-27 11:11, Stephen Brewin wrote:
Hi
As I recall, the intent of having separate projects for many of the
components developed under the James umbrella was to satisfy the
requirement that they should be independent of James Server. While this
remains a requirement, separate repositories are needed for each project
to allow separate release versions and schedules. It also influences our
maven module layout and how dependencies might be better managed.
I can not talk about the drivers for separate projects, but I understand
those projects as a way to be able to use them without the full james
server. It is also a way to force developers to think in terms of API
contracts between those projects.
Before proceeding with a discussion of how to simplify the development
workflow, we need to decide if the original requirement still holds.
Prospective solutions will be quite different depending on this answer.
Cheers
--Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
