commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <bay...@generationjava.com>
Subject Re: [io] FilenameUtils needs work
Date Tue, 30 Dec 2003 17:28:46 GMT


On Tue, 30 Dec 2003, Jeremias Maerki wrote:

>
> On 30.12.2003 17:01:24 Henri Yandell wrote:
> >
> > Agreed. If no one has the itch, we should shelve it.
> >
> > I would just list it as: Not going for 1.0 and we wouldn't include it in
> > the 1.0 tag. It can stay in its current place in CVS I think. We got away
> > with this a lot in Lang, having packages that didn't deploy even though
> > they were in HEAD etc.
>
> I like putting new stuff into a sandbox directory until it is ready.
> Leaving it where it is means that the person applying the CVS tag must
> be pretty careful. Just an observation, not a proposal.

When we migrate over to commons-proper cvs, we can keep this one alive for
sandbox work. Lang did this too, though it does seem to cause confusion
sometimes.

The people checking the release have to be careful too :)

> > Are there any methods in there that are worth pushing? Or just skip the
> > whole thing for 1.0 and when someone turns up with the itch we can hit
> > them with all the difficulties and as a group solve them?
>
> IMO we can skip the whole thing. But checking FilenameUtils and
> FileUtils I realize we don't have any methods in FileUtils that do
> extension handling (getExtension, removeExtension).
>
> The only problem I see is people who might use methods from
> FilenameUtils today. But that should motivate them to step in. :-)

Yep :) Until 1.0 we don't support anything is my view.

Hen


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


Mime
View raw message