NBICommandLineOptions
NBI Command-Line Options
NBI engine supports the following command-line options:
| Command-Line Option | Argument | Example | System property | Description | Note |
|---|---|---|---|---|---|
| --look-and-feel | <laf-classname> | --look-and-feel org.jvnet.substance.SubstanceLookAndFeel | UiUtils.LAF_CLASS_NAME_PROPERTY | this option will instruct the engine to use a custom look and feel. | The specified look and feel should be present in engine's classpath. |
| --target | <uid> <version> | --target nb-ide 6.0.0.0.0 | Registry.TARGET_COMPONENT_UID_PROPERTY Registry.TARGET_COMPONENT_VERSION_PROPERTY | this option will instruct the engine to "target" a specific component. I.e. the components tree will be filtered to display only the target component, its "parent" component(s) and the components it depends on. | This option is used when running the engine from Windows' Add/Remove Programs application. |
| --locale | <locale_name> | --locale ru_RU | this option will instruct the engine to execute in the specified locale, useful for i18n testing, etc. | ||
| --state | <state_file> | --state /tmp/state.xml | Registry.SOURCE_STATE_FILE_PATH_PROPERTY | this option will instruct the engine to load components' states from the specified statefile. | This option can be combined with --silent. |
| --record | <state_file> | --record /tmp/state.xml | Registry.TARGET_STATE_FILE_PATH_PROPERTY | this option will instruct the engine to record the components' states to the specified statefile upon exiting the installer. Using this option should be considered a principal way for generating statefiles. | |
| --silent | --silent | this option will instruct the engine to execute in silent mode, i.e. no GUI will be shown, not questions will be asked. All data required can be taken from the statefile supplied with the --state option. | |||
| --create-bundle | <bundle-jar-file> | --create-bundle /tmp/netbeans-6.0-bundle.jar | Registry.CREATE_BUNDLE_PATH_PROPERTY | this option will instruct the engine to create a redistributable bundle containing the selected components instead of installing them. The bundle at this moment is an executable jar file, all the selected components will be contained within this bundle, thus there will be no need for any network connection. | |
| --userdir | <directory> | --userdir ~/.nbi | Installer.LOCAL_DIRECTORY_PATH_PROPERTY | this option will instruct the engine to use <directory> as the working NBI directory. | By default, it is ~/.nbi on Unix and %USERPROFILE%/.nbi on Windows |
| --platform | <platform-name> | --platform solaris-x86 | Registry.TARGET_PLATFORM_PROPERTY | this option will instruct the engine to use <platform-name> as the target platform for creating the bundle | If it is not set, target platform is determined on the current platform of java process |
| --registry | <registry-uri> | --registry http://bits.netbeans.org/download/6.0/beta1/latest/registry/registry.xml | Registry.REMOTE_PRODUCT_REGISTRIES_PROPERTY | this option instruct the engine to use the specific registry either during creating the bundle or withing the installation process | |
| --properties | <properties-file> | --properties /tmp/some.properties | this option instruct the engine to load the engine properties (System) from the specified file | ||
| --bundle-properties | <properties-file> | --bundle-properties /tmp/bundle.properties | Installer.BUNDLE_PROPERTIES_FILE_PROPERTY | this option instruct the engine to put properties from the specified file to the creating bundle file | this option requires installer to be in create-bundle mode |
| --ignore-lock | --ignore-lock | Installer.IGNORE_LOCK_FILE_PROPERTY | this option instruct the engine to ignore the lock file (~/.nbi/.nbilock) that can exist in the current engine working directory and continue installation without a warning | ||
| --suggest-install --suggest-uninstall --force-install --force-uninstall | Registry.SUGGEST_INSTALL_PROPERTY Registry.SUGGEST_UNINSTALL_PROPERTY Registry.FORCE_INSTALL_PROPERTY Registry.FORCE_UNINSTALL_PROPERTY | these options affect initialization of product statuses when the overall registry is constructed | |||
| --nospacecheck | --nospacecheck | SystemUtils.NO_SPACE_CHECK_PROPERTY | this option disables free space checking on the installer panels (welcome, selection, destination, summary) | ||
