Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 66103 invoked from network); 22 Mar 2008 10:57:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Mar 2008 10:57:49 -0000 Received: (qmail 28064 invoked by uid 500); 22 Mar 2008 10:57:46 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 27977 invoked by uid 500); 22 Mar 2008 10:57:46 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 27968 invoked by uid 99); 22 Mar 2008 10:57:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Mar 2008 03:57:45 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates 209.85.146.183 as permitted sender) Received: from [209.85.146.183] (HELO wa-out-1112.google.com) (209.85.146.183) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Mar 2008 10:57:07 +0000 Received: by wa-out-1112.google.com with SMTP id k34so2283707wah.10 for ; Sat, 22 Mar 2008 03:57:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=8kkFEpza8T5OYliY5exGV04cvoDmrTradrCWbmA61TA=; b=mp/3ah64X9yJx/HJVBohpotsdifXKhxoTraChVwVTlFKeH6gMbCD1Q6vwAc8Gn9/qD48P9nyF0XC6KW3OUNamwE4SJ+vzDAkBY52tusVP47NFTRblr228nOPq6a5YZ8shOEq2oK5mA2dDJIOUogF3I0Fr2yQ58mgPlGvtWwnY4M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Sg7jamot6U0bNZ3oXGBJU04+DJN6GBfB4gkLAN769ZSkoBebA2XK+t9lS36tZjyJzvvHOOl5POngsWaVi3ZFrTYxbdBzuQYR1YnHZPs+XTV21BorCbYdiGYYo2o47XoMJRw/i//8kCHpNe3lue8Kk8Y2139fHlgxgymb5yWdqak= Received: by 10.114.173.15 with SMTP id v15mr7360799wae.63.1206183438625; Sat, 22 Mar 2008 03:57:18 -0700 (PDT) Received: by 10.114.144.18 with HTTP; Sat, 22 Mar 2008 03:57:18 -0700 (PDT) Message-ID: <31cc37360803220357i625f355t3f39cca5b6013b4c@mail.gmail.com> Date: Sat, 22 Mar 2008 03:57:18 -0700 From: "Henri Yandell" To: "Jakarta Commons Developers List" Subject: Re: [CLI] Release CLI2 ? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <31cc37360803211914i7499438eq9d91880e435b0e7f@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Mar 21, 2008 at 9:11 PM, Tobias Bocanegra wrote: > > > hi all, > > > i'm working on a project that is using CLI2 for an interactive console > > > application. To my understanding, CLI2 is not released nor is a > > > snapshot available in the m2 repository. so i'm wondering what is > > > missing for a CLI2 release? What does the community think of a CLI2 > > > release? is it used by many projects at all? > > > > We need to get the damn thing out. :) > > > > > > > i would volunteer to work on the issues that prevent a release. > > > > In no particular order: > > > > * Solve, or recommend moving to 2.1, all the 2.0 issues in JIRA. > > * Make sure M2 is happily building the site, distribution etc. > i just ran "mvn install" and "mvn site" and these seems to work ok. Yep, does seem to be pretty much there. > > * Make sure the checkstyle/pmd/findbugs aren't full of problems. > checkstyle is currently not enabled. but i can do this later. I just enabled checkstyle + findbugs for maven1. I tend to use them there as I get OOMs in maven2. > since i don't know the very details of the code yet, maybe you or > another CLI team members can point me out which of the issues are > show-stoppers for a 2.0 release, and i will try to contribute patches. It's an odd situation where no one knows the details of the code very well. Anything that has been recognized as not a blocker for a 2.0 release is in 2.1, entirely likely other 2.0 issues could be moved to 2.1 too. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org