Fixed issues

This section lists fixed issues for the BlackBerry® Java® Plug-in for Eclipse®.

If you used Windows® 7 or Windows Vista™, when you installed the BlackBerry Java Plug-in for Eclipse using the full installer into the default location (c:\Program Files\Eclipse) you were unable to import signature files. (580248)

If you installed the Eclipse IDE for Java EE Developers, after you installed the BlackBerry Java Plug-in for Eclipse, some help files were missing. (428621).

When you ran a BlackBerry device application project in BlackBerry® Java® SDK 4.2.1, if you selected Launch Mobile Data System Connection Service (MDS-CS) with simulator in the BlackBerry Smartphone Simulator launch configuration, the BlackBerry® MDS Connection Service was not found. (427117).

When you changed the preprocessor directives in a BlackBerry device application project, after you built theBlackBerry device application project, the preprocessed file did not reflect the changes. (425921).

When you installed an update to a BlackBerry Java SDK from the BlackBerry update site, the updated BlackBerry Java SDK did not appear in the list of installed JREs under Preferences > Java > Installed JREs. (425666).

When you installed an external BlackBerry® Smartphone Simulator, the BlackBerry Smartphone Simulator did not apear in the Debug Configurations > Simulator > Device drop-down list. (425662).

When you debugged a BlackBerry device application project on a running BlackBerry Smartphone Simulator, if you used Javaloader to load the .cod file on the BlackBerry Smartphone Simulator, the running BlackBerry Smartphone Simulator could not connect to the debug file. (424726).

When you created a BlackBerry Smartphone Simulator launch configuration, if you specified the MEID, the MEID did not appear in the command line on the Run Configurations > Simulator > Advanced tab. (413051).

When you clicked Debug as > Running BlackBerry Simulator to debug a BlackBerry device application project on a standalone BlackBerry Smartphone Simulator, the BlackBerry Java Plug-in for Eclipse did not package the BlackBerry device application project. (411143).

If you created a BlackBerry device application project that had a Java dependency, when you clicked Debug As > BlackBerry Simulator the BlackBerry device application project failed to launch. (411043).

When you selected a single BlackBerry device application project and clicked Debug As > BlackBerry Simulator, if a debug configuration already existed for the BlackBerry device application project, the BlackBerry device application project failed to launch. (411031).

When you used linking to import a BlackBerry device application, if an icon file was excluded, when you clicked Run As > BlackBerry Simulator, the excluded icon still appeared on the BlackBerry Smartphone Simulator.(356504).

When you ran a selection of BlackBerry device application projects from the context menu, the BlackBerry Java Plug-in for Eclipse automatically created a new launch configuration. If you modified the launch configuration and re-ran the same selection of BlackBerry device application projects, the original launch configuration ran instead of the new launch configuration. (410744).

If you created a new BlackBerry device application project from an existing source, when you renamed the BlackBerry device application project the error message "new project name overlaped the location for old project name" and the Finish button was disabled. (403237).

When you updated the BlackBerry Java SDK, if you opened a BlackBerry device application project that was created in an earlier version of the BlackBerry Java SDK, when you created a new BlackBerry device application project, the BlackBerry Java Plug-in for Eclipse used the earlier version of the BlackBerry Java SDK. (401436).

When you linked a legacy BlackBerry device application project to an Eclipse workspace, if you linked the same BlackBerry device application project to a different Eclipse workspace, a build error was generated. (398729).

In a BlackBerry device application project , if you changed the project-specific JRE™ to the workspace default JRE, when you selected Run as > BlackBerry® Smartphone Simulator, the wrong BlackBerry Smartphone Simulator launched. (393884).

When you debugged a BlackBerry device application project on a BlackBerry device that was connected to your computer, if you selected Prompt for missing debug files, when the debugger encountered missing files, error messages displayed. (391965).

When you debugged a BlackBerry device application project on a BlackBerry device that was connected to your computer, when you selected Prompt for missing debug files and Don't ask again, the setting was cleared when you disconnected from the debug session. (391933).

When you ran the BlackBerry Java Plug-in for Eclipse in a non-English version of Windows® with a version of the BlackBerry® Java® SDK that was earlier than 5.0, you might have encountered a preverification error on file names that contained the pound currency (£) character when the /bin folder was passed to RAPC. (358837).

When you localized a BlackBerry device application project, if the .locale_interfaces folder or .res folder was missing, no error message displayed. You had to create the folders manually. (281311).


Was this information helpful? Send us your comments.