To configure runtime the Kit Manager bundle uses the following system properties:
System Property |
Default Value |
Description |
|---|---|---|
mbs.script.base |
OSGi folder of framework |
Use it to specify the script base URL. |
mbs.bundles.base |
../../../bundles |
Use it to specify the bundle base URL. |
mbs.kitlist.url |
kits.txt |
Use it to specify the static kits' list. |
mbs.kitlist.dirs |
bin/pscripts/demo |
Use it to specify the directories to inspect for install scripts. |
mbs.kitman.startup |
bin/pscripts |
Use it to specify the location of a kit's install script, which will be automatically executed at framework startup. The install script can be placed at a URL starting with file:/, http:// or ftp://, or in the location, set with the mbs.exec.base system property. |
mbs.kitman.startup.nobkgrd |
false |
Set this property to true if you do not want to execute an install script at framework startup in a background thread. In such as a case, the command input will remain blocked until the install script execution ends. |
mbs.kitman.debug |
false |
Use it to enable debug about the Kit Manager's operation. |
mbs.kitman.console |
false |
Set this property to true to have generated debug printed in the framework console. |
mbs.kitman.waitPackagesRefresh |
true |
Configures whether 'refresh packages' is called synchronously or asynchronously after installing/uninstalling a kitman script. Its value is true by default, which means that operation is guaranteed to finish before the kitman script ends (synchronous call). |