Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43DBEB05.2000605@eircom.net>
Date: Sat, 28 Jan 2006 22:07:01 +0000
From: Rory Winston <rwinston@eircom.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [net] JDK 1.4+ Branch?
References: <20060128183205.40475.qmail@minotaur.apache.org>
 <ce1f2ea80601281049x3e2e81a3x23acfbbced34d9cd@mail.gmail.com>
 <43DBD5BF.9030902@eircom.net> <43DBDCA9.90908@javactivity.org>
In-Reply-To: <43DBDCA9.90908@javactivity.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Steve

Agreed that JDK 1.3 (and previous) is still important to support. My 
question is: is it desirable to put a 1.4+ version on HEAD and relegate 
JDK 1.3 to a separate branch, or do we not want to get into separate 
branch maintenance?

R

Steve Cohen wrote:

> Rory Winston wrote:
>
>> Hi
>>
>> I have been following the email threads re: JSSE and FTPS 
>> functionality. I think that this might be a good point to consider 
>> introducing a version of Commons-Net that uses JDK 1.4+ as a 
>> baseline. My reasoning is as follows:
>>
>> * We could remove the (oro) jar dependency;
>> * FTPS support would not necessitate a separate (JSSE) jar dependency;
>> * It could be a good opportunity to "clean up" the threading code and 
>> socket handling, and make use of NIO;
>> * It also may be easier to incrementally add new functionality, such 
>> as Proxy support
>>
>> Of course, JDK-1.3-compatible releases could still continue on HEAD, 
>> or we could move the 1.4+ branch to HEAD and the 1.3 code to a 
>> maintenance branch.
>>
>> As a simple proof-of-concept, I have set up a sandbox branch and made 
>> some minor enhancements, including:
>>
>> * Changing oro-dependant code to use Java regex code instead
>>
>> Any comments?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>>
> The only negative I can find is that our contributor of the FTPS stuff 
> badly wants 1.3 compatibility.  And I have a feeling that he's not the 
> only one.  1.3 is not yet End of Life according to Sun, although it 
> will be soon.  My sense is that we lag Sun by some interval of time on 
> these issues.  I don't think we're going to be able to get away with 
> saying "no more enhancements for JDK1.3" for awhile.  So this will 
> probably mean maintaining two branches for some time.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org