Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 3299 invoked from network); 12 Sep 2006 23:03:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2006 23:03:51 -0000 Received: (qmail 36906 invoked by uid 500); 12 Sep 2006 23:03:49 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 36820 invoked by uid 500); 12 Sep 2006 23:03:49 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 36809 invoked by uid 99); 12 Sep 2006 23:03:49 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Sep 2006 16:03:49 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from ([209.237.227.198:33078] helo=brutus.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id 94/12-05218-3EC37054 for ; Tue, 12 Sep 2006 16:04:03 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6C786714349 for ; Tue, 12 Sep 2006 23:00:24 +0000 (GMT) Message-ID: <60236.1158102024441.JavaMail.jira@brutus> Date: Tue, 12 Sep 2006 16:00:24 -0700 (PDT) From: "David Leal (JIRA)" To: commons-dev@jakarta.apache.org Subject: [jira] Commented: (CLI-113) generate ant task automatically from CLI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/CLI-113?page=comments#action_12434307 ] David Leal commented on CLI-113: -------------------------------- The similar product JSAP, provide such utility, it simplify a lot the process of defining the input argument syntax, because you don't need a Java class for defining the its syntax. You can look on the following link: http://www.martiansoftware.com/jsap/doc/ch14.html as you can see they use xstream and probably from it generates an equivalent Java source class. The important point is to define a quite general XML syntax. As you can see the JSAP syntax is language depend, becuase the help node, a better solution would be to define a help_key, so the application will look in to properties file, via ResourceBundle class. I would be a kind of Inverse of Control (IoC) for CLI, you define what you want in a configuration file, and the application instance the corresponding parser after XML validation the Java validation will be simpler. David Leal > generate ant task automatically from CLI > ---------------------------------------- > > Key: CLI-113 > URL: http://issues.apache.org/jira/browse/CLI-113 > Project: Commons CLI > Issue Type: Improvement > Environment: Operating System: other > Platform: Other > Reporter: pklein > Priority: Minor > Fix For: 2.1 > > > I'd like to suggest an enhancement to CLI - > 1) have CLI generate a schema of the command line options it expects > 2) write some code to read the schema, and generate an ant task > Any project using CLI would then be able to easily produce an ant task. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org