fab:start — starts the specified FAB
META-INF/maven/GroupID/ArtifactID/pom.xml. Any transitive dependencies that are shared (for example, by being marked as provided or because the dependency is already packaged as an OSGi bundle), are deployed as separate OSGi bundles in the container.
fab:start, the runtime attempts to start all of the corresponding bundles, starting with the leaves of the dependency tree and working its way up the tree to the FAB's bundle. In particular, this implies that any OSGi services, blueprint XML files, and Spring XML files in the dependent OSGi bundles are activated in the appropriate order.
Table 9.3. fab:start Arguments
|Displays the online help for this command|
|Specifies, in milliseconds, how long to wait for the FAB bundle to start up. Default is |
|The bundle ID of the FAB.|