From commons-dev-return-12324-qmlist-jakarta-archive-commons-dev=jakarta.apache.org@jakarta.apache.org Wed Jul 24 13:26:06 2002 Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 29989 invoked from network); 24 Jul 2002 13:26:04 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 24 Jul 2002 13:26:04 -0000 Received: (qmail 15225 invoked by uid 97); 24 Jul 2002 13:26:19 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 15049 invoked by uid 97); 24 Jul 2002 13:26:16 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 15025 invoked by uid 98); 24 Jul 2002 13:26:15 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Reply-To: From: "Berin Loritsch" To: "'Jakarta Commons Developers List'" , , "'Avalon Developers List'" Subject: RE: [CLI] Making Option Extensible Date: Wed, 24 Jul 2002 09:25:42 -0400 Message-ID: <003d01c23315$9c8fba30$ac00a8c0@Gabriel> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <3D3EA6B7.7060408@apache.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] > > John Keyes wrote: > >>John Keyes wrote: > >>... > >> > >>>I was thinking about how this would affect the current > implementation > >>>and I winced at all of the changes to the constructors and the > >>>addOption methods. > >> > >>Have you looked at the Avalon CLI? > >>We want to move it to Commons, this can be a good opportunity to > >>compare > >>approaches and point of integration. > > > > I have looked at this before but I didn't see any stuff > > in there that CLI does not already have. What are the benefits of > > using Avalon CLI versus Commons CLI? > > I'm sending this also to the Avalon Developers List, so that > the authors > can reply better to this question. I heard a rumor that Commons CLI does not support the GNU standards on CLI options. GNU standards have already affected a large number of standard software options for UNIX based Oss, and it is a decently thought out standard. The basic gist is this: --help -h The double-dash signifies a long option name, and any arguments for the option follow using spaces to separate them from the option name. The single-dash signifies a short option name (a single character), and any arguments follow directly after the option name. Examples of options with arguments: --definition foo=bar -Dfoo=bar --file myfile.xml -fmyfile.xml We can also combine a number of options after one dash: -hDf foo=bar myfile.xml All arguments are separated by a space, and are resolved in the order that the option is listed. Whether you support the decision to use GNU standards or not, they should not be ignored because they aren't Apache standards. I also would argue that the "Java" option style really has no standard. All options (short or long) have one dash, but there is no way to represent a more readable version of a short option or shortcut the typing for a long option. They are what they are. -- To unsubscribe, e-mail: For additional commands, e-mail: