Maintenance Release for the BlackBerry Java Plug-in for Eclipse v1.3

Java Development

I am pleased to announce a maintenance release for the BlackBerry® Java® Plug-in for Eclipse® v1.3. This maintenance release addresses customer feedback on the new plug-in by improving simulator support for multi-core 64-bit Windows® 7 workstations.

In case you missed the post about the release of the BlackBerry Java Plug-in for Eclipse v1.3, this version of the plug-in provides support for the latest Eclipse version 3.6 (Helios). It’s designed to help with debugging performance and marks the start of a new way to distribute plug-ins by simplifying access and installation of SDKs. As stated in the post above, we will no longer provide an update site for the Java Plug-in for Eclipse 1.3 and BlackBerry® WebWorks™ on Eclipse, but we will keep update sites available for component pack downloads.

New features of the BlackBerry Java Plug-in for Eclipse v1.3 include:

  1. Eclipse 3.6 (Helios) support with a new BlackBerry Java Development Eclipse perspective
  2. New Application Wizards to get new BlackBerry® smartphone applications up and running quicker
  3. A dynamic “Getting Started Welcome Page” to provide relevant and updated information of key development resources
  4. Update Notification to let you know when new versions are available for download
  5. Improved debugger performance for faster breakpoints and evaluation
  6. MacOS X Java Plug-in for Eclipse feature parity

We encourage you to replace the current BlackBerry Java Plug-in for Eclipse v1.3.0 with this maintenance release, especially if you are using Windows 7. Download the latest plug-in from the Developer Zone today.

Let us know if you have any questions in the comments!

Join the conversation

Show comments Hide comments
+ -
  • the_paulus

    Does this release include new simulators, specifically simulators with OS6?

  • Derek Konigsberg

    The major issue involving linking between library projects that target different BB JDK versions still does not appear to have been fixed, and this is probably the biggest reason why I simply cannot step up to the v1.3 plugin yet without making life difficult. Simply Googling has shown that you’ve introduced and fixed this issue in the past, and now its back again.

    I first described it here:

    And someone from RIM later confirmed it here:

    Hopefully its just an update to the component packs, which is separate from the core of the plugin. Just please fix it already.

  • Derek Konigsberg

    Okay, I think I may have actually found a workaround for that multi-JDE-version bug mentioned again in my last post.

    The issue is, assuming you have two projects:
    TestLib_BB45 (JRE 4.5.0) and TestLib_BB46 (JRE 4.6.0) with a dependency between them, the plugin will invoke RAPC in such a way that it tries to include JRE 4.5 and 4.6 in the build path when building TestLib_BB46.

    The workaround is to, instead of using a project dependency, give a library dependency to the class folder “TestLib_BB45/bin”. Whenever the Eclipse workspace is built, this will give TestLib_BB46 a way to resolve its references on the other library. And when packaging for the simulator, it seems to work okay.

    • Anonymous

      Just to give anyone reading this an update – this does work for getting the build to run, but when deploying to the simulator it seems that it will no longer deploy all library versions (ex: if you have lib_45, lib_46, lib_47, lib_50, lib_60 and main_app, it will deploy *only* main_app and lib_45). This remains even after verifying that all dependencies are configured correctly.

      Beyond this: I tried making a wrapper .exe to replace “rapc.exe”, which simply stripped out the extra net_rim_api.jar paths after the first one. While it did resolve the build issue, it then introduced this same issue as described above.

      Something that occurs to me – the main application is by necessity targeted to the earliest platform version – in the example above “main_app” must be configured for 4.5; in previous eclipse versions, it would not matter – the deployment would go to the simulator with all libraries specified in the run configuration. But perhaps in this case, it only pushes up to the max library version used in the build configuration of the main app? That sounds a bit convoluted – but I can’t think of any other reason for the beahvior to change in this way.

  • Javamon

    You expect us to download 400 MB everytime you update the plug-in? Seriously?

  • Anonymous

    I see that this build does not fix the (rather major) issue that prevents us from testing against multiple platform versions when building a project with libraries targeted at varying platform versions. Eg – a 4.6 lib project, 5.0 lib project, and a main app project. Unless ALL libraries target a single platform — the app will not run . This was mentioned in the forums, and confirmed by a development adviser as reproducible.

    Is there any plan to correct this? For those of us with larger/more complex projects who support multiple libraries across multiple platforms, this is preventing adoption of 1.3 entirely.

  • ekke

    good to see that you’re working on java sdk 🙂

    but it’s frustrating again for this new release only to get a FULL installer and NO update from updatesite.
    so I always have to spend valuable time to configure this eclipse installation 😦

    this is a really drawback….

  • Indrakusumax

    It’s not easy to download the Eclipse since it is stored on HTTPS so If my download is failed it can’t continue and I must restart the download again. I’ve tried 8 times and because of the bandwidth of my country are not good as yours it was very painful. Please take a respon to my problem. Thank You.

  • Jakub Nietrzeba

    Anything about plugin which works in Linux environment?

  • Jkoorts

    What a farce of a MR! I still cant close the simulator. This is a documented bug! I still have to exit the whole IDE to close the simulator. what a waste of 400MB download.

  • Jkoorts

    still cant close the emulator. to clean the persistent store, exit eclipse, browse your computer for the persistent data, delete them, start eclipse, run your app. And you call this a maintenance release? Are you kidding me?

  • Ramzeska

    Can`t install into existing BBEclipse SDK on Mac Os X 10.6.6.
    I don`t want to make fresh install again, import all my favorite plugins, settings and etc.

  • andrey

    In simulator (at least, if simulate 9800) of this brand-new release:
    * add contact through “Contacts” application
    * remove it
    * enjoy exception

  • Vacchis

    1) I developed applet and run on simulator 9800 torch (OS 6.0) All OK
    2) Using Desktop to download on device. All OK; icone showed on device . .
    3) I try to run . . . but does’nt run … Why ????

    Note: I don’t use APIs signed …

  • Xavo

    currently I experience huge problems downloading version 1.3 from blackberry website. I don’t really know what is the reason for this. I click “Download” button and empty screen is shown.

    I try the same for the plug-in version 1.1 and everything goes fine.

    Did I miss something?

  • Anup

    How can I access Simulator for 9000 in this new release ?

blog comments powered by Disqus