ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18060] New: - add aliases for common Ant options, particularly -projecthelp
Date Mon, 17 Mar 2003 11:48:00 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18060>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18060

add aliases for common Ant options, particularly -projecthelp

           Summary: add aliases for common Ant options, particularly -
                    projecthelp
           Product: Ant
           Version: 1.5.2
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: ian_springer@hp.com


I use the -projecthelp option quite often, but it is annoying to type, since 
it's so long. I think a one-letter alias for it (similar to the -q/-v/-f/-l  
aliases for -quiet/-verbose/-buildfile/-logfile) would be extremely cool. I 
suggest -?, since it's intuitive and it's not currently in use. Also, you 
might as well make -h an alias for -help while you're at it. For that matter, 
why not do all the options, at the least the common ones - like CVS does.  I 
would suggest something like the following:

  -help, -h              print this message
  -projecthelp, -?       print project help information
  -version, -V           print the version information and exit
  -diagnostics           print information that might be helpful to
                         diagnose or report problems.
  -quiet, -q             be extra quiet
  -verbose, -v           be extra verbose
  -debug, -d             print debugging information
  -emacs, -e             produce logging information without adornments
  -logfile, -l <file>    use given file for log
  -logger   <class>      the class which is to perform logging
  -listener <class>      add an instance of class as a project listener
  -buildfile, -f <file>  use given buildfile
    -file        <file>           ""
  -D<property>=<value>   use value for given property
  -propertyfile, -p <name> load all properties from file with -D
                         properties taking precedence
  -inputhandler  <class> the class which will handle input requests
  -find <file>, -F       search for buildfile towards the root of the
                         filesystem and use it


Regards,
Ian

Mime
View raw message