The General tab shows the content that's applicable to all build configurations for a project.
Package Information
The package information uniquely describes your application. Package information includes the following elements:
This field contains a universally unique application identifier (UUID) 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 setup application, and it may have multiple values for each language.
This field, combined with the Package Build ID, specifies the full version number for the application. This version number is a series of four numbers separated by decimals (for example 1.0.5.357) in this format: Major.Minor.Revision.Build. The default is 1.0.0.1. This number is interpreted as the minimum API level that your application requires. You must have an installed API level that covers the specified platform version.
The versionNumber specifies the first one, two, or three numbers of the version number. For example, 10, 10.1, or 10.2.1. The buildId is the fourth part of the package version. The first number must be an integer from 1 to 65535, inclusive. The remaining three numbers must be an integer value from 0 to 65535. Leading zeroes are not permitted. For example, 1.0.1.130 is valid, but 1.01.1.130 isn't valid because "01" is not supported.
This is an optional field. You can set the Package Build ID field using the Momentics IDE or the blackBerry-nativepackager tool. If you want the Momentics IDE to update this number whenever you perform a build, use the Use internal build number XML element in your bar-descriptor.xml file. You can set this element on the Source tab.
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.
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 Momentics IDE sets the initial value to 1. When the build ID is read from a file, the Package Build ID field is disabled. If the file referenced in the <buildIdFile> element doesn't exist, the Momentics IDE displays a warning.
The default is 1.
Author Information
The author information represents the name and identifier information associated with the project for the specified debug token.
The name of the author associated with the project. This name is typically the name of the author used for signing, and it must match the developer name of your development certificate.
The default is Example Inc.
The unique ID assigned by the signing authority. Your 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.
Import the name and identifier from a debug token.
API Level
The API Level identifies which platform version is used when you package your application. There are two options:
Problems
The problems area identifies the number of warnings and errors in the bar-descriptor.xml file.
Related Settings and Actions
The Related Settings and Actions area has links to wizards to help you configure the Momentics IDE, targets, package signing, and debug tokens.