Startup should handle the most common arguments: -h --help / -v --version

Jody Garnett added a comment - 06/Mar/09 7:13 AM We need to look at the UDIGApplication and check if we can access command line parameters; if not we should mark this as WONTFIX. But I think we can: - http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/msg29215.html We use the Apache Commons CLI for our command line parsing. It works nicely for us, was easy to implement and maintain. Take a look at Platform.getCommandLineArgs() usage in IDEWorkbenchAdvisor to see what is available in the Eclipse framework. It is a simple implementation that does the job. David Kyle http://richclientplatform.blogspot.com

John Hudson added a comment - 13/Mar/09 10:37 PM This is quite simple using the above links I have added a snippet of code (see attached .patch file) which looks for "--help", "-h", "--version" or "-v" and System.outs upon finding any of these as command line arguments. This patch is not a complete fix.

John Hudson added a comment - 13/Mar/09 10:38 PM Foundation of work, this can be used to gather the command line arguments and display appropriate output for each.

Andrea Antonello added a comment - 14/Mar/09 5:03 AM the help looks like: NAME udig SYNOPSIS udig.exe [OPTIONS] [-vmargs [VM_OPTIONS]] DESCRIPTION uDig is an open source (LGPL) desktop application framework, built with Eclipse Rich Client (RCP) technology. OPTIONS --help, -h Print this help and exit. --version, -v Print version number and exit. -data <workspacePath> Sets the path of the workspace on which to run udig. -nl locale Defines the name of the locale on which uDig is running (ex. -nl IT will force uDig to run with Italian user interface). -clean Cleans cached data used by the OSGi framework and Eclipse runtime. Try to run Eclipse once with this option if you observe startup errors after install, update, or using a shared configuration. -consoleLog -debug Mirrors all errors to standard output. Usefull to find odd behaviours and report them to developers. -vm <vmPath> The location of Java Runtime Environment (JRE) to use to run uDig. VM_OPTIONS -Xmx<memory size> Set maximum Java heap size (ex. -Xmx1200m sets it to 1200 megabytes). and the version like: Version Information: uDig version: 1.2M3 Java VM: 1.6.0_11 OS: Windows Vista x86 Closing issue

Jody Garnett added a comment - 25/Mar/09 7:32 PM - edited This is not working for me on windows? I checked the source code and the patch has been applied. It is kind of doing something: when I run "udig.exe -h" the splash screen shows; and then the application stops - but the help text is not displayed anywhere. I went and checked the logs (on the off chance standard out was used and that is where the information was being sent; but I did not see anything there).

Jody Garnett added a comment - 04/Mar/10 5:03 PM Andrea still no progress on this for windows; could you do a windows specific test and open up a text file using notepad that has the help instructions? Could we somehow ask the user to press a key when they are done reading (so the CMD window does not close right away?) If you really don't care mark this issue as closed; windows users are not likely to open the command line.