Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (athena.apache.org: domain of simon@qcg.nl designates
 217.148.84.61 as permitted sender)
Message-ID: <5367656C.7000300@qcg.nl>
Date: Mon, 05 May 2014 12:18:20 +0200
From: Simon IJskes - QCG <simon@qcg.nl>
Organization: Quality Consultancy Group b.v.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Peter <jini@zeus.net.au>, dev@river.apache.org
Subject: Re: Modularization
References: 
 <CAJuA6A5cQ5fx9jZT5A4R=-6b1NAh-izpvREzFSK9ggBQvDOzCg@mail.gmail.com>
	  <53614787.4090005@qcg.nl> <1398896971.2616.11.camel@Nokia-N900>
In-Reply-To: <1398896971.2616.11.camel@Nokia-N900>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 01-05-14 00:29, Peter wrote:
> ----- Original message -----
>  > On 30-04-14 02:02, Dennis Reedy wrote:
>  >
>  > > A this point I'm soliciting opinions and thoughts. Note that using
>  > > Gradle is certainly an option here, the breakout into multi-modules is
>  > > not tied to Maven, it's based on accepted conventions. I chose Maven
>  > > because it was the quickest (for me) to get going.
>  >
>  > Good thing! Just to show support! I applaud a separation into multiple
>  > source trees, as a starting point for modularization.
>  >
>  > Any change we can re-apply your effort on trunk while maintaining
>  > subversion history? i.e. 'svn mv' commands?
>
> Lets wait until after confirming the modular build structure though.

How do you define this milestone? On what step, decision, or positive 
outcome shall we wait?

Gr. Simon