Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <448DBE63.7020200@toolazydogs.com>
References: <448D84ED.2000602@gmail.com> <448DBE63.7020200@toolazydogs.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <20EA8245-13E3-442E-9F91-AFF56633DD5D@iq80.com>
Content-Transfer-Encoding: 7bit
From: Dain Sundstrom <dain@iq80.com>
Subject: Re: [RTC] Initial reorganization of the javamail source tree.
Date: Mon, 12 Jun 2006 12:30:03 -0700
To: dev@geronimo.apache.org

+1

-dain

On Jun 12, 2006, at 12:20 PM, Alan D. Cabrera wrote:

> It does need an RTC since there's a lot of changes here.
>
> +1
>
>
> Regards,
> Alan
>
> Rick McGuire wrote:
>> Not sure if this really requires an [RTC] or not, but it doesn't  
>> hurt.  The patch attached to this Jira:
>>
>> http://issues.apache.org/jira/browse/GERONIMO-2107
>>
>> Is the initial checkin for the new javamail providers repository.   
>> The bulk of this diff is just the javamail-transport module pulled  
>> from the 1.2-dead branch.  The most significant change is the  
>> mail-1.3 module, which builds an "uber-jar" containing the  
>> javamail-spec jar and the javamail-provider jar.
>>
>> This reorg is being done in stages.  Once this code is in place,  
>> the following additional steps need to be made:
>>
>> 1)  Remove javamail-transport from the 1.2 build and change the  
>> javamail-transport dependencies to be the new javamail-provider jar.
>> 2)  Add the javamail 1.4 implementation to the specs tree.
>> 3)  Create javamail-provider-14. and mail-1.4 modules in the  
>> javamail repository.
>> 4)  Create a javamail 1.4 plugin version.
>>
>> Rick