I'm very happy to review and commit patches Brian - but I need someone to be doing the majority of the activity. The issue tracker for Commons moved, which is why you're finding that it's closed.
http://issues.apache.org/jira/browse/CLI I've gone as far as to keep things generally in the right versions release wise. I also know there are others who would like to help with a release, but we're looking for someone to step up and drive the activity. So this is a great email to see :) Hen On 5/12/07, Brian A. Egge <[EMAIL PROTECTED]> wrote:
Hello, I've been using the Commons CLI library for various projects for several years now. The CLI library is nearly inactive, and I would to see that changed. The current version of CLI, 1.0, was released over two years ago. Since then, some work was done on a new 2.0 release, but that was never finished. The bug tracker is full of bugs relating to the 1.0 release, but there is no way to open new issues. Checking out the 1.0 branch, it apparently was branched some time after the 1.0 binary was created. Commons CLI is useful to many Java projects, and I think it's only going to become more visible once Commons is made a TLP. What I'd like to do: 1) Bug fix the 1.0 branch, and close some of the existing bug reports. 2) Get a 2.0 release, and re-open the/a bug tracking system. The 1.0 branch has enough features for most projects, and it's the release that nearly everyone uses, so I think it's worthwhile putting some maintenance effort into it. Since the bug tracker is closed for new bugs, and I can't find any active committers for this library, I haven't been able to contribute patches. Is there someone who has the time to help revive this project? I'm happy to do as much as a non-committer can do, but I need someone to help by reviewing and integrating patches updating the bug tracker, etc.. Cheers, Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
