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 Stefano Bagnara <ap...@bago.org> on 2008/06/24 19:17:36 UTC
deployments, configs and duplicate content
Hi all,
I just noticed that
phoenix-deployment/src/conf/
and
spring-deployment/src/main/config/james/
have the same content: or better, I should say that spring-deployment
have the content we had in phoenix-deployment some months ago.
Having clones of them lead to desynchronization.
Any suggestion on how should we deal with this in our multimodule setup?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: deployments, configs and duplicate content
Posted by Bernd Fondermann <be...@googlemail.com>.
On Tue, Jun 24, 2008 at 7:17 PM, Stefano Bagnara <ap...@bago.org> wrote:
> Hi all,
>
> I just noticed that
> phoenix-deployment/src/conf/
> and
> spring-deployment/src/main/config/james/
>
> have the same content: or better, I should say that spring-deployment have
> the content we had in phoenix-deployment some months ago.
>
> Having clones of them lead to desynchronization.
First of all, this is intentional. (Whether this is good or bad or
should be changed is another thing.)
I refrained from copying them over from phoenix-deployment at build
time, because changes in them might trigger more work within the
spring-deployment module and there where times when they had to be
adopted.
This is also mentioned in the HOW-TO.
>
> Any suggestion on how should we deal with this in our multimodule setup?
I am very open to any good ideas on how to improve this.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org