Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Sender: jcarman@carmanconsulting.com
In-Reply-To: <4F564C74.7000303@apache.org>
References: <4F564C74.7000303@apache.org>
From: James Carman <james@carmanconsulting.com>
Date: Tue, 6 Mar 2012 20:43:06 -0500
Message-ID: 
 <CALznzY7xGod0yq357CVfMFVe3bOz2vH5mDfmiRz8Go4mpbJJ+g@mail.gmail.com>
Subject: Re: [VOTE] Promote [csv] to Commons proper
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

I still think it should be renamed, but I think I lost that battle.
It's not just for comma-separated values.  I'd rather us come up with
a more generic name.  I'm +1 for moving it out of the sandbox.  It
needs a bit of polish before a release, though, IMHO.

On Tue, Mar 6, 2012 at 12:42 PM, Emmanuel Bourg <ebourg@apache.org> wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers, a CSV API looks incomplete to me without this
> - Examine the feasibility of adding a simple bean mapping feature
> - Extract the unicode unescaping feature as an implementation of
> java.io.Reader, and maybe contribute it to Commons IO
> - Improve the documentation
>
>
> [ ] +1 Promote it!
> [ ] -1 Let it crawl in the sandbox because...
>
> Emmanuel Bourg
>

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