Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <46CA5629.8040806@erdfelt.com>
Date: Tue, 21 Aug 2007 11:04:09 +0800
From: Joakim Erdfelt <joakim@erdfelt.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070607)
MIME-Version: 1.0
To: archiva-dev@maven.apache.org
Subject: Re: MRM-462 progress
References: <810396CD-67FD-418D-8D68-2A75B9645EFB@apache.org>
In-Reply-To: <810396CD-67FD-418D-8D68-2A75B9645EFB@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have a decent raft of new code coming in as part of MRM-463 (metadata 
stuff), can you hold off until that commit comes in?

- Joakim

Brett Porter wrote:
> I decided to use a branch for the configuration split since I thought 
> it could be (at least partially) contentious, and is at least quite 
> disruptive. I won't have a problem merging the lot down to trunk once 
> completed.
>
> Please review the changes if you are interested in it - I'm confident 
> that the changes outside the webapp are solid since all the tests are 
> passing again (I've added some coverage that was missing in 
> archiva-configuration, the rest are much less consequential changes).
>
> The next step is to change the webapp, and I'l be adding tests there 
> to ensure that the functionality is working. This could take a little 
> longer.
>
> I'm worried at how much the implementation details of the 
> configuration have leaked out throughout the application - something 
> to review later on.
>
> Thanks,
> Brett
>