Re: Commons - CLI 2.0

Hi there, Yep - I don't know of anyone with strong interest in CLI2, which should be viewed as an experimental unreleased branch imo. I'm really interessted in it, cause I'm using this state im my project, cause the usage is very simple and gives me exactly what i need...

Re: Commons - CLI 2.0

Actually I think Hadoop might also have a dependency on CLI-2.0, so it may be good to get an official release out for them as well: http://svn.apache.org/viewvc/hadoop/core/trunk/ivy/hadoop-core.pom?revision=726872view=markup I dont know anything about CLI, but I may be able to assist someone

Request sandbox access

I just submitted a big patch to DbUtils to update the API to use Java 5 features (generics, varargs). http://issues.apache.org/jira/browse/DBUTILS-48 There really aren't very many bugs left in this project; almost all of them have patches attached. I think it wouldn't be much work for

Re: Commons CLI

Hi Henri, my workload still looks depressing so I would appreciate it very much if you could cut the release. Having said that I want to update the pom.xml because a release would not work properly. After a couple of rejected release candidates I'm the local expert for the maven release-prepare

Re: Proposal: Commons SAX

Hi, On Wed, Dec 31, 2008 at 2:55 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Until we come up with consensus on where (Commons, Xerces or Cocoon) we should place this proposed library, I'd like to start putting some bits together in the Commons Sandbox. I've now set up a project skeleton

Re: [compress] SANDBOX-246 remaining Findbugs issues

On 2009-02-05, Christian Grobmeier grobme...@gmail.com wrote: * ZipOutputStream contains some proteted static final byte[] constants This means any subclass could modify them. Findbugs suggests to make the package private. Ant couldn't do that because of backwards incompatibility, but

Re: [compress] SANDBOX-246 remaining Findbugs issues

The svn merges were more or less painless, the only conflict I got was in UnknownExtraField because the commons-compress version uses m_foo fields where Ant uses foo (likely because of Avalon/Peter Donald coding style). If you could do that - yes, thats cool then. I suggest we add the

Re: Commons - CLI 2.0

Maybe the release would get it off the ground. I'm thinking that we stop thinking of CLI 1.x and CLI 2.0 (branches of one product); but rather CLI and CLI2; ie) two separate components with their own sites. That might free each to stop being hamstrung by the other. Hen On Thu, Feb 5, 2009 at

Re: Proposal: Commons SAX

On Wed, Dec 31, 2008 at 1:25 PM, Rahul Akolkar rahul.akol...@gmail.com wrote: On Wed, Dec 31, 2008 at 8:55 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, Until we come up with consensus on where (Commons, Xerces or Cocoon) we should place this proposed library, I'd like to start

[VOTE] CLI 1.2 release (RC1)

Pushing out a first RC for CLI-1.x. It's a bit of an odd duck in that it uses CLI2's site. --- Tag: https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC1 Site: http://people.apache.org/~bayard/cli-1.2-rc1/ Binaries: