Bug 847272 - CLI doc - Incorrect examples for executing a script with argumets
Summary: CLI doc - Incorrect examples for executing a script with argumets
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Documentation
Version: JON 3.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Deon Ballard
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-10 11:28 UTC by Filip Brychta
Modified: 2014-10-23 12:29 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-01 00:33:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Filip Brychta 2012-08-10 11:28:33 UTC
Description of problem:
Example 11 and Example 16 from http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Dev_Writing_JON_Command-Line_Scripts/common-actions.html are incorrect.


Example 11:
following line:
rhqadmin@localhost:7080$ exec -f echo_args.js --args-style=named x=1, y=2

correct version:
rhqadmin@localhost:7080$ exec -f echo_args.js --args-style=named x=1 y=2
(no comma between arguments)



Example16:
localhost:7080(rhqadmin)> exec --style=named -f /absolute/path/to/myscript.js -s named x=1 y=2 y=3

correct version:
localhost:7080(rhqadmin)> exec --args-style=named -f /absolute/path/to/myscript.js x=1 y=2 y=3

-s is not a valid option for exec command (maybe it was removed?? - not sure) so following sentence 'This can be done using the -s option, which, much like the --args-style option with the rhq-cli.sh command' is not true any more.



Tested on JON311ER1

Comment 1 Deon Ballard 2013-03-01 00:33:20 UTC
Mass closure.


Note You need to log in before you can comment on or make changes to this bug.