General page

This page shows the content that is applicable to all build configurations for a project. You can access this page by expanding a project from the Project Explorer, double-clicking on the file bar-descriptor.xml, and then selecting the General page.

For convenience, quick links to related preference pages, wizards, and other actions are also available. All options listed here are optional unless otherwise specified in the description of the option.

Option XML element Description Default
Package Information N/A Required. Describe the package information associated with your application. N/A
Identifier <id> Required. Identifier associated with the application. This field contains a universally unique application identifier that must be unique across all BlackBerry 10 applications. We recommend that you use a reverse DNS-style name for the ID, such as com.example.MyExampleApplication. This identifier name is displayed in the BlackBerry 10 application installer, and it may have multiple values for each language.

Specify a value for this element when you intend to run your application on a device using a debug token. This value should match the Author value from your debug token.

The package identifier for the project.
Version, Build Number <versionNumber>, <buildId> Together, these fields specify the full version number for the application, which is a series of four numbers separated by decimals (for example 1.0.5.357) in this format: Major.Minor.Revision.Build

The Version string specifies the first one, two, or three parts of the version number. Each number must be from 0 through 999. The Build Number is the fourth digit segment of the package version. This number must be an integer from 0 to 65535.

Each time you sign your application, you must change at least one segment of the version number.

If you use the Build Number field, it's up to you to change it manually; if you want the IDE to update this number automatically, use the Use internal build number setting.

You can also specify the build number using the buildId command-line option when you package your application using the blackberry-nativepackager tool. If you specify a build number in both the bar-descriptor.xml file and the blackberry-nativepackager tool, the value given to the blackberry-nativepackager tool is used.

1.0.0 and 1, respectively
Create build number file <buildIdFile> Extract the current value of <buildId> into a file named buildnum in the project, and then automatically manage the build ID when packaging .bar files. If there is no <buildId>, then the IDE sets the initial value to 1. When the build ID is read from a file, the Build Number field and the Create build number file button are disabled. The IDE will display a warning if the file referenced in the <buildIdFile> element doesn't exist. Initial value to 1
Author Information N/A Show the author name and identifier information associated with the project for the specified debug token. Specify values when you intend to run your application on a device using a debug token. N/A
Name <author> The name of the author associated with the project. This is typically the name of author used for signing, and it must match the developer name of your development certificate.

Specify a value for this element when you intend to run your application on a device using a debug token. This value should match the Author value from your debug token.

Example Inc.
Identifier <authorId> The unique author ID assigned by the signing authority. Your author identifier is the same for all your debug tokens.

Specify a value for this element when you intend to run your application on a device using a debug token. This value should match the Author Id value from your debug token.

N/A
Set From Debug Token N/A Import the author name and identifier from a debug token. For more information about debug tokens, see Signing page. N/A
Problems N/A Identify the number of warnings and errors in the bar-descriptor.xml resource. N/A
Related Settings and Actions N/A Direct access links to dialogs to help you configure the BlackBerry 10 Native SDK, targets, package signing, and debug tokens. N/A
API Level N/A Required. Identfies which platform version is used when you package your application. There are two options:
Use the API level from the project settings (recommended)
The API level that you set in the New Project Wizard or the project properties determines the platform version number.
Explicitly set the platform version.
Specifies the platform version number. It must have four numeric segments, such as 10.1.0.0. You must have an installed API level that targets the specified platform version.
Use the API level from the project settings

Last modified: 2013-12-21

comments powered by Disqus