[
https://issues.apache.org/jira/browse/JAMES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653268#comment-14653268
]
Matthieu Baechler commented on JAMES-1588:
------------------------------------------
> Are you thinking to put this backends module at the same level as server,
> mailbox...?
Exactly
> I proposed the same kind of module some time ago, but we decided to not
> follow that way. Looking back , it sound like this would not have been the
> best thing to do (release management...).
You are right one this point : it makes building James even more difficult. But
duplicating libraries doesn't seems a good idea neither.
> The other way would be to merge all james modules in one structure to make a
> single release. This may be worth to start a discussion on the maliling list.
Thank you very much to bring this subject to discussion : we are struggling for
months to find a good workflow to work on James. The split repositories is a
hell to manage, you can see our james-parent repository
(https://github.com/linagora/james-parent) where we aggregate git repositories
with git submodule. But everything is much harder that way and if we start a
discussion on the mailing list about repositories merge, I will be happy to
push my arguments there.
> Create a project to centralize Cassandra tools
> ----------------------------------------------
>
> Key: JAMES-1588
> URL: https://issues.apache.org/jira/browse/JAMES-1588
> Project: James Server
> Issue Type: Improvement
> Reporter: Tellier Benoit
>
> As we are starting to develop data tools based on Cassandra, we realized we
> would use tools we defined for the Cassandra mailbox. But :
> - We don't want a dependency to the cassandra mailbox in our data-cassandra
> module
> - We do not want to duplicate information.
> Hence we prefer introducing a new module, that centralize tools needed by
> modules relying on Cassandra ( for now the Cassandra mailbox, and the
> data-cassandra module, Cassandra MPT module ).
> As we think this can be a common need to several backend implementation, we
> want to create a dedicated project for centralizing back-end tools, that will
> be calles james-backends. Each back-end ( eg : cassandra, jpa, hbase, etc ...
> ) will create its submodule in it and will use it in other places (MPT,
> Mailbox, james (server) ).
> Let us now if you have any feedback on this proposal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
