You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/02/14 09:01:32 UTC
DO NOT REPLY [Bug 33554] New: -
[commons-launcher] Print targest instead of usage
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33554>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33554
Summary: [commons-launcher] Print targest instead of usage
Product: Commons
Version: Nightly Builds
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P2
Component: Sandbox
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: Stephan.Strittmatter@gmx.de
It would be more usable for end-user, if commons-launcher would print a list of
targets on missing or wrong targets.
It would be probably the best, if the target-name and (if available) the
description of the targets are printed on console.
Something like:
Error: xxx is not a valid target
Usage: "myApp" [options] [-] target [-D<name>=<value>...] [-] [application
arguments...]
where options include:
target:
a do something A
b do something B
c do something B
-help Print this usage statement
-launchfile <file> The XML file to use (the default is "launcher.xml")
-executablename <name> The executable name to print in this usage statement
-verbose Print stack traces with error messages
Probably the flags -launchfile, -executablename and -verbose could then also be
hidden for "productive" systems.
BTW, there is no component "launcher" in the component list. So I assigned it to
sandbox.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org