Version 1.3 of Dragonfly, the BUG SDK: Best Release Ever

We released the latest version of the BUG SDK today. This has a number of improvements over the last version, and it's our best version ever. I highly recommend upgrading to this version as there are a number of improvements in stability and functionality.

To upgrade, I suggest starting with a fresh install of Eclipse 3.4.2, which can be found on the Eclipse Downloads Page . Then follow the directions on our SDK Install Guide using the Update Site method. You can also do the full install, but the advantage of using the update site is it makes upgrading easier in the future. If you already know what you're doing, go the Bug Downloads Page for the update site url or the full install files.

There are a few changes and features I would like to point out. For a detailed list of features and defects (or if you're just nerdy like that), you can also read the SDK Release Notes .

The most major change for 1.3 is it is fully compatible with Eclipse 3.4. Prior releases worked with Eclipse 3.4, but were never fully supported or tested. As a side-note, Dragonfly 1.3 also works with Eclipse 3.3.2, so if you're not ready to move to Eclipse 3.4, you can still use the latest version of Dragonfly.

Dragonfly 1.3 works with older BUGs. If you're running an older version of BUG Linux, then you've been stuck with version 1.1 of Dragonfly. Now all BUG users can enjoy the latest version. Also, Javadocs for PhoneME and the BUG Libraries are now integrated into Dragonfly.

Probably the most useful feature was added by kgilmer . It's a way to attach your console view in the SDK to a running BUG's OSGi console. To bring up the console, you right click on a BUG connection in the My BUGs view and select "Show OSGi Console":

Finally, if you look at the SDK Releases page where we keep past releases including those for testing and development, you'll notice our version numbers have changed format slightly. The new build number scheme is Major.minor.release.build where build is the letter v followed by a timestamp followed by the build type. For example the full build number of the latest SDK release is 1.3.3.v200905151522_P. This is Major version 1, minor version 3 (we update this with every release cycle), release 3 (we update this with each QA cycle), and finally build v2000905151522_P, which is the build made on May 15, 2009 at 15:22 for Production release (P).

I hope you enjoy writing BUG Applications with the latest SDK. Please remember to share your work with the rest of the community . And if you have questions, don't hesitate to post to our forums .