Clad User Manual: Difference between revisions
Jump to navigation
Jump to search
(36 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
The framework scans the command line looking for the first argument that can be mapped to a command. | The framework scans the command line looking for the first argument that can be mapped to a command. | ||
The mapping process involves scanning the classpath and looking for classes implementing the [https://github.com/NovaOrdis/clad/blob/master/src/main/java/io/novaordis/clad/command/Command.java Command interface]. The current version does not introspect all classes, but just those whose simple class name match the following pattern: <tt><commandName>Command</tt>. | The mapping process involves scanning the classpath and looking for classes implementing the [https://github.com/NovaOrdis/clad/blob/master/src/main/java/io/novaordis/clad/command/Command.java Command interface]. The current version does not introspect all classes, but just those whose simple class name match the following pattern: <tt><commandName>Command</tt>. All arguments between the wrapper name and the command name are interpreted as global options. All arguments following the command name are interpreted as command options. | ||
All arguments between the wrapper name and the command name are interpreted as global options. | |||
All arguments following the command name are interpreted as command options. | |||
<pre> | <pre> | ||
wrapper [global-options] command [command-options] | |||
</pre> | </pre> | ||
= | =Subjects= | ||
< | <blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | ||
:[[clad User Manual - Concepts|Concepts]] | |||
:[[clad User Manual - How to Implement a Command Line Application|How to Implement a Command Line Application]] | |||
</blockquote> |
Latest revision as of 18:17, 8 November 2016
Internal
Overview
The framework scans the command line looking for the first argument that can be mapped to a command.
The mapping process involves scanning the classpath and looking for classes implementing the Command interface. The current version does not introspect all classes, but just those whose simple class name match the following pattern: <commandName>Command. All arguments between the wrapper name and the command name are interpreted as global options. All arguments following the command name are interpreted as command options.
wrapper [global-options] command [command-options]