Fixed issues

These are the fixed issues for the BlackBerry Java Plug-in for Eclipse v1.5 for Windows.


Workspaces with multiple JRE dependencies could not be built. (1395477)

If you wanted to install multiple versions of the BlackBerry Java SDK, you had to specify your login credentials for each SDK. (545417)

When you installed the BlackBerry Java SDK in Eclipse 3.5.1, a warning about unsigned .jar files displayed. (427122)

When you upgraded from the BlackBerry Java Plug-in for Eclipse 1.x to 1.1.2, signing keys were not transferred automatically. (579957)

If you moved the BlackBerry Java Plug-in for Eclipse to a new location, you could not use the BlackBerry Smartphone Simulator. (545814)

If you started debugging a project with breakpoints and then changed the BlackBerry JRE, the debugger did not provide output. (557517)

When you clicked Debug as > Running BlackBerry Simulator to invoke a debug session for a BlackBerry device application, the debugger did not terminate when the BlackBerry Smartphone Simulator terminated. (410786)

After you debugged a BlackBerry device application in the BlackBerry Smartphone Simulator, if you ran the application from Eclipse and then closed the simulator, the simulator did not stop. (512588, 532712)

When you hot-swapped your BlackBerry device application on the BlackBerry Smartphone Simulator, if you removed the icon for the application and set the idle and rollover icons externally, when you re-deployed the application to the BlackBerry Smartphone Simulator and then closed the application, the application icon on the simulator reset to the default icon. (1063282)

When you tried to configure the BlackBerry Smartphone Simulator to use a file media card, the simulator did not recognize the media card. (543853)

When you tried to clear files from a simulated media card in the file system by using the clean simulator feature, the media card was not cleared and no error was displayed. (543845)

If you configured a simulator media card and, in the SD Card Image field, you specified a path that includes a space, an error occurred indicating that there was an unrecognized argument. (543816)

When the BlackBerry Smartphone Simulator was running and you created a new run configuration that uses a different BlackBerry JRE or simulator/device, the BlackBerry Java Plug-in for Eclipse prompted you to close the simulator that was currently running. If you closed the simulator manually and then tried to dismiss the prompt, the new simulator launch configuration did not start. (543775)

When you ran a MIDlet on the BlackBerry Smartphone Simulator and then made a change to the application, when you reloaded the application on the simulator, the change was not reflected on the simulator display and you encountered an exception when you closed the application. (560007)

If you used a 64-bit operating system, you cannot close a BlackBerry Smartphone Simulator that you launched outside the BlackBerry Java Plug-in for Eclipse. (565499)

If you configured your BlackBerry application project to automatically sign .cod files after packaging, when you ran or debugged the application, the BlackBerry Signature Tool signed keys that were marked as optional. (533697)

If you removed a .key file from a BlackBerry application project, the associated entries in the BlackBerry_App_Descriptor.xml file were not removed. (528274)

When you ran a BlackBerry device application, if the application did not require signing, the BlackBerry Signature Tool prompted for signing. (467422)

When you ran Windows 7 with Eclipse 3.5.0 or 3.5.1, if you changed the BlackBerry_App_Descriptor to remove a resource file that was marked as invalid (for example, if you changed the file externally) from the Application Icons section, you encountered a stack overflow error. (601594)

You could create two identical preprocessors in the BlackBerry_App_Descriptor.xml. (538991)

If you tried to clean a project more than once immediately after packaging, it did not complete successfully. (537756)

When you created a BlackBerry application project that was a library and ran the library application on the BlackBerry Smartphone Simulator, the library application had an associated default icon. (520519)

When you specified the properties for a BlackBerry application project, some fields accepted special characters (for example, @, $, %) that were not valid in the Eclipse development environment. (242681).

When you imported a BlackBerry application project by linking the files rather than by copying the files, and you shared the project using the Perforce plug-in for Eclipse, when you synchronized the project, you encountered an error. (476444)

When you updated the BlackBerry Java Plug-in for Eclipse from version 1.1.1 to 1.1.2 and you launched a BlackBerry application project that you created in version 1.1.1, the default JRE in the workspace or in the project was not updated. (560511)

When you used the Import Existing Projects wizard to import by linking a project that was created by using the BlackBerry JDE Plug-in for Eclipse 1.0, when you built the project, you encountered an exception that a .preprocessed folder already exists. (538764)

The following properties in the BlackBerry_App_descriptor.xml file did not correlate with the application type. (520325)
  • Icons for Library type applications (if present before the switch) should be unavailable and not passed to RAPC.
  • Warnings for main(String[]) missing is valid only for the BlackBerry Application (CLDC) type.
  • Alias list makes sense only for Libraries, so it should be unavailable for other application types.
  • Auto-run on startup for Library applications makes sense if there is a libMain(String[]).

When you created a localized BlackBerry device application, after you created resource files for a locale other than English, when you launched the application, you encountered errors. (1092910)

If you created a BlackBerry application project that had a library dependency and the library had language resource files, you could not set the Resource Title ID in the application project properties. (522311)

When you specified a Description ID for a locale resource in the BlackBerry_App_Descriptor.xml file of your BlackBerry application project, the description did not display if you built your application with BlackBerry Java SDK 5.0. (506631).

When you created a launch configuration and you changed the default JRE, the description from the new project BlackBerry JRE was not updated in the Runtime JRE dialog. (557094)

When you developed a BlackBerry device application using BlackBerry Java SDK 4.7, 4.6.x, or 4.5, Eclipse would exit when you hovered the mouse over certain classes or methods (such as PersistentContent.addListener) to view the related Javadoc description. (501375, 565695, 566182)

If there were no preprocessor directives defined in your BlackBerry application project, the Select All and Deselect All options were still available. (560344)

When you imported an .epf file that you created in the BlackBerry Java Plug-in for Eclipse 1.1.1 into the BlackBerry Java Plug-in for Eclipse 1.1.2, the import failed. (518912)

When you profiled your BlackBerry 7.0 application project, when you attempted to open the BlackBerry Profiler view, you encountered the error message, "Could not create the view: An unexpected exception was thrown.". (2486071)

When you created aBlackBerry 7.0 application project with two icon sources, for example, one for the core application and one for an alternate entry point, when you debugged your project on a BlackBerry smartphone, the icon for the alternate entry point was not displayed. (2023628)

When you created a run configuration, if you specified a path name that contained a space in the Simulator > Memory > Branding data text box, the resulting command line text was missing the enclosing quotation marks ("). (1077308)

Next topic: Known issues

Was this information helpful? Send us your comments.