Command-line packaging parameters

The following table lists the parameters that are available when you package your app using the BlackBerry WebWorks SDK command-line tools.

Parameter Description
archive

Specifies the name of the app archive file (.zip) to package.

With BlackBerry 10 WebWorks SDK, you can choose to use an archive file or just specify your app's folder location. For more information, see Package your app.

-g

Signs your app by using the keystore password.

-o

Saves the output files to the specified folder. If you do not use this parameter with a folder, or if this parameter is not specified at all, the output files are saved to the simulator and device subfolders in the current working directory.

-s

Saves the source files. By default, if you specify this parameter without a folder, the source files are saved to the src folder within the same path as the app archive. If you specify a folder, the source files are saved in the src folder within the folder that you specify.

-v

Displays verbose messages during compilation, and is optional.

-h

Displays command line help, and is optional.

-d

This parameter sets the developer mode, which is used by Web Inspector and the debug token.

The -d option will always enable Web Inspector, which allows you to open your app in the Google Chrome browser and use Web Inspector to debug your code.

--buildId or -b

For signed apps, specifies the build number. Typically, this number should be incremented from the previous signed app.

If you specified a version number in the config.xml file, the build number you specify becomes the fourth digit of the version number. For example, either 1.2.0 or 1.2.0.1 (in config.xml) become 1.2.0.7 if you specify a build number of 7.

If you do not specify a build number, the version number stays the same (if it is four digits long) or a fourth digit of 0 is added (if it is three digits long). For example, 1.2.0.1 remains the same, and 1.2.0 becomes 1.2.0.0.

--params or -p

Specifies the path to a JSON file that can contain additional parameters to pass to downstream command line tools (such as blackberry-nativepackager and blackberry-signer). For an example of a parameters file, see the params-example.json file, which is stored in the root of the BlackBerry WebWorks Packager.

Sample usage:

If you use the BlackBerry WebWorks Packager behind a firewall, you might have to specify the proxy settings so that you are able to successfully sign your app. You can include a params.json file, which is stored in the root of the BlackBerry WebWorks Packager that looks like the following:

{
    "blackberry-signer": {
        "-proxyhost": "host",
        "-proxyport": "port",
        "-proxyusername": "user name",
        "-proxypassword": "password"
    }
}

When you package your app with the bbwp command and the --params params.json option, the proxy settings are passed to blackberry-signer.

Last modified: 2014-03-10



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus