Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Commons Net 1.5 / 2.0 Releases
Date: Mon, 25 Aug 2008 15:05:45 +0200
Message-ID: 
 <460801A4097E3D4CA04CC64EE64858480730F7CC@ism-mail03.corp.ad.wrs.com>
In-Reply-To: <8833dc800808220745w1bf7a8a0w1a78719d9c2dadf5@mail.gmail.com>
Thread-Topic: Commons Net 1.5 / 2.0 Releases
Thread-Index: AckEZex4liU+8YpBRpSuX9OcHbYChgCTPIAw
References: 
 <460801A4097E3D4CA04CC64EE648584805B5157A@ism-mail03.corp.ad.wrs.com>
 <25aac9fc0805190829p38c47f28gf1c5609a4836ca3c@mail.gmail.com>
 <8833dc800805191030w1eb3607bgd144bfc90accaeb1@mail.gmail.com>
 <25aac9fc0805191036s54403727yfe62e72aa6551383@mail.gmail.com>
 <8833dc800805201243v5fd87c5ftc8ec95214693d83a@mail.gmail.com>
 <4833552A.2030801@eircom.net>
 <8833dc800805210054h7c974c47l2d48a8704ed82ea3@mail.gmail.com>
 <483493A8.7070008@eircom.net>
 <8833dc800805212302s7342a55du53b3410a72948f10@mail.gmail.com>
 <8833dc800805270231s41882dfaue6b8fe051f245263@mail.gmail.com>
 <8833dc800808220745w1bf7a8a0w1a78719d9c2dadf5@mail.gmail.com>
From: "Oberhuber, Martin" <Martin.Oberhuber@windriver.com>
To: "Commons Developers List" <dev@commons.apache.org>

Thanks Niklas.

The backward compatibility question you mention was about the
suggestion to refactor the Commons Net "small protocol"=20
implementations into separate packages each:

> Basically there's no problem to deliver a=20
> commons-net-2.0-legacy.jar that contains something along
>=20
> package org.apache.commons.net;
> class Echo extends org.apache.commons.net.echo.Echo { ... };
>=20
> > I'm all in favor of code cleanup and refactoring when
> > I see clear advantages, but not at any price.

I was not in favor of such a costly, breaking change which
doesn't buy much, so I'd vote for going forward towards
a release. Can you put up a release candidate?

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
=20
=20

> -----Original Message-----
> From: Niklas Gustavsson [mailto:niklas@protocol7.com]=20
> Sent: Friday, August 22, 2008 4:46 PM
> To: Commons Developers List
> Subject: Re: Commons Net 1.5 / 2.0 Releases
>=20
> On Tue, May 27, 2008 at 11:31 AM, Niklas Gustavsson
> <niklas@protocol7.com> wrote:
> > On Thu, May 22, 2008 at 8:02 AM, Niklas Gustavsson=20
> <niklas@protocol7.com> wrote:
> >> On Wed, May 21, 2008 at 11:27 PM, Rory Winston=20
> <rory.winston@gmail.com> wrote:
> >>> I meant to say "out of the project". It was moved to=20
> test/ after the
> >>> discussion.
> >>
> >> Great, so it seems we agree :-) However, the class is still in
> >> src/main, not in src/test:
> >>=20
> http://svn.apache.org/repos/asf/commons/proper/net/branches/NE
> T_2_0/src/main/java/org/apache/commons/net/tftp/TFTPServer.java
> >>
> >> Should I move it to the test directory?
> >
> > If no one objects I'll go ahead and move it to src/test.
>=20
> Alright, better later than never I guess. As no one objected, I'll go
> ahead and commit that change.
>=20
> Is there anything else that would be needed before a 2.0 release?
> Previously in this thread there was some discussions around backward
> compatibility, but no conclusion seems to been reached. Do we need to
> discuss this further?
>=20
> /niklas
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>=20
>=20

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