|<< Back to previous view|
Need a dry-run for start-local-instance to see what the generated jvm commandline would be
[GLASSFISH-16291] Document new option for start server commands Created: 30/Mar/11 Updated: 04/Apr/13 Resolved: 04/Apr/13
|Reporter:||Byron Nevins||Assignee:||Mike Fitch|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Participants:||Byron Nevins and Mike Fitch|
I added a new boolean option,
to start-local-instance and start-domain
What it does is do everything EXCEPT actually creating and running the JVM. Instead it returns the HUGE commandline that it WOULD have used to start the server.
D:\gf\v3>asadmin start-local-instance -n i1
|Comment by Mike Fitch [ 07/Feb/13 09:58 PM ]|
Neither start-domain nor start-local-instance show these options in their usage message:
asadmin> start-domain --usage
Both commands appear to accept -n, but neither will accept --dry-run (or --dryrun for that matter).
Please let me know how to proceed. Should we document just the -n option?
|Comment by Byron Nevins [ 07/Feb/13 10:34 PM ]|
That's because the official name of the option is
I'll change it to "dry-run" right now. It should be working in the next build you get.
|Comment by Mike Fitch [ 04/Apr/13 09:52 PM ]|
Added writeups to start-domain and start-local-instance.
These additions were included in main-docs build 4.0-b27, which started getting picked up by GlassFish builds as of revision 61152 (03-Apr-2013).