Unable to start the BlackBerry Java Plug-in for Eclipse from the command prompt when the plug-in installation name/workspace path contains spaces. (1964450)

Rename the existing Eclipse binary, and then create the proper soft link to address the issue.

When the plug-in installation folder path/workspace name contains spaces, the plug-in does not launch after installation. (1964358)

Avoid using a folder name with spaces as the destination folder for the plug-in or the workspace.

Deleting locale resources throws an illegalArgumentException while debugging on a BlackBerry device. (2082063)

No work around is available at this time.

When you debug dependent projects using the default JVM for Mac, an error displays. (2393734)

Change the JVM of the dependent projects to SDK 7.0.

In Eclipse, when you select a variable in the detail pane, the detail formatter issues an error message. (1036094)

None.

When you debug your BlackBerry device application by using step filtering, Filter by Package does not work. (900918)

After you select Filter by Package, click Window > Preferences > Java > Debug > Step Filtering; check the Use Step Filters check box.

When you hot-swap a BlackBerry device application that uses resource keys, if you change a resource key, the application is not updated when you resume hot-swapping. (762467)

Close the application before hot-swapping.

When you debug your BlackBerry device application by hot-swapping, if you remove a field from a persistent instance, when you relaunch your application, hot-swap does not stop. (743487)

None.

If you create two BlackBerry launch configurations, the BlackBerry Java Plug-in for Eclipse does not prevent you from launching both sessions. Both sessions might not start. (534772)

Do not start multiple debug sessions.

When you create a BlackBerry device launch configuration and select the option to attach to a specific device, the BlackBerry Java Plug-in for Eclipse does not prevent you from starting to debug without specifying the device. In addition, the list of available devices does not reflect the devices that are currently attached even after selecting the option to refresh the list. (535402)

Do not create a device launch configuration that attaches to a specific device without specifying the device.

When you use hot-swap to debug a BlackBerry device application that uses the persistent store, if you remove fields from a persistent instance, hot-swap fails to stop after the second (or subsequent) fields are removed. (743487).

Close the application before removing multiple fields.

When you debug a BlackBerry device application using the BlackBerry Profiler View, if you click the rows inside the view multiple times, Eclipse freezes or closes. (854940)

Close the debugging session or restart Eclipse.

When you debug a BlackBerry device application on a BlackBerry device, after your application stops at a break point, when you click resume, the debugger may stop responding. (856280).

Restart the BlackBerry device and begin a new debug session.

When you view the Project > BlackBerry menu, an option for Clean Simulator appears, but is not functional. (860542)

No work around is available at this time.

When you restart Eclipse after the preprocessor is configured, the restart dialog appears again. (2378705)

None.

When you get a restart dialog because the preprocessor is being configured, the preprocessor hook could not be configured correctly dialog appears. (2378705)

None.

When you package a BlackBerry application project that requires signing, after you sign the application once, you are not prompted for a signature again until repackaging is required. When you run the same application, you are always prompted for a signature. (1113779)

When you create a BlackBerry application project that depends on a Java project, you may not be able to package the application or load it on a BlackBerry device. (1051705)

When you add a BlackBerry application project as a dependency to a Java project, you encounter an error. (1015170)

Use a BlackBerry project of the library type instead.

After a user upgrades to a newer version of a BlackBerry device application, a duplicate entry for the application exists in Options > Applications, but only one version is accessible from the Home screen. (725671)

Build the .alx and .jad files to generate the same Application ID when the application is installed on a BlackBerry device.

On a computer running Mac OS X 10.6 (Snow Leopard), in Eclipse, after you make changes to a resource file in the Resource Editor, when you click Validate the console does not display any output. (2406318)

None.

When you rename a BlackBerry device application package while an original locale file is open in the Resource Editor, the original locale file is copied, not moved. (368943).

Close the original locale file in the Resource Editor before you rename the package.

When you use a version of Windows that is not English, when you build a BlackBerry device project that contains locale resources, a pound currency symbol (£) is appended to the file name of the .crb file that is created in the /bin folder of the project. (494006)

Use an English version of Windows, or in Windows, configure the Regional and Language Options to change the language for non-Unicode programs to English.

On a computer running Mac OS X, when you install the BlackBerry Java Plug-in for Eclipse, if you specify a very long installation path name or workspace path name, when you run an application on a BlackBerry smartphone, the application fails to load and no error dialog or prompts are displayed. (2606740)

Make the installation and/or workspace path name less than 128 characters.

On a computer running Mac OS X 10.7 (Lion), if there are spaces in the installation path for the BlackBerry Java Plug-in for Eclipse, the preprocessor does not work. (2429514)

Reinstall the plug-in in a path with no spaces.

When you specify the version number of a MIDlet application on the BlackBerry Application Descriptor screen for a BlackBerry project, if you type spaces or special characters in the Version field, the characters are accepted but do not generate an error. (1103499)

Use a version definition that complies with the MIDlet specification by using three numeric segments, for example 1.2.3.

If you create a MIDlet name that is 255 characters long, when you enter the name in the Name of main MIDlet class field or in the Title field of an Alternate Entry Point (AEP) on the BlackBerry Application Descriptor screen, the packaging process fails. (1103724, 1103725)

Create MIDlet names that are shorter than 255 characters.

In the BlackBerry Application Perspective, if you select text in the Eclipse editor while Convert String to Hex is enabled the conversion fails, when you change to another perspective. (1037354)

None.

When you connect your BlackBerry device to a computer by using the USB cable, if you type an incorrect password when the BlackBerry Desktop Software launches, the USB connection hangs. (1010746)

To reset the connection, remove the device from the USB cable, reboot the computer, reattach the device to the USB cable. After you enter the correct password in the BlackBerry Desktop Software, right-click and select Force Quit.

When you activate the Drag and Drop feature in the Resource Editor so that you can drag and drop keys into the source code window, the feature does not work. (369175)

In the Resource Editor, use the Add Key button.

When you remove a BlackBerry Java SDK from a launch configuration, you encounter a NullPointerException and the launch configuration is corrupted or, when you update the BlackBerry Java SDK without changing the launch configuration, you are prompted to save unsaved changes. (560259)

Delete the launch configuration and create a new one.

When you use BlackBerry Java SDK 6.0.0.29, if you link an entry to your contacts, after you change it and save it as a new contact, you encounter an UncaughtIllegalArgumentException. (743694).

Upgrade to a later version of the BlackBerry Java SDK.

If there is white spaces in the path preprocessor, it will not run. (2428514)

Avoid using white space in the path preprocessor.