It finally happened. After 7 years of working on EclipseME, my little hobby project is finally growing up and becoming the official implementation of the Eclipse Mobile Tools for the Java Platform (MTJ) project. This is really a big win for everyone involved with EclipseME. For users, it means more support from the larger MTJ project team. For myself, it means… more support from the larger MTJ project team. For device manufacturer and carriers, it means that there is an official Eclipse Foundation project to interact with. This brings with it all of the benefits of a well-organized foundation that really understands the needs of corporations when working with open source software. With the involvement from Motorola, Nokia, Research In Motion and other device manufacturers, MTJ should be able to move forward much more quickly than it could move with the small EclipseME development team.

(more…)

Version 1.7.0 had a number of builder problems that have caused people quite a bit of trouble. Because of those problems, it has been determined that it would be better to remove that version until a fixed version can be made available. Version 1.7.0 has been removed from Sourceforge and the update site has been reverted to version 1.6.8. If you are currently using version 1.7.0 without problems, you are free to continue using the release until the next release is available. If you are having problems and would like to revert, please follow the instructions to remove the 1.7.0 release and follow the standard installation instructions to install version 1.6.8.

I apologize for the problems with the 1.7.0 release and hope to get a fixed release out soon.

In the Version 1.6.6 release, the ability to launch via an arbitrary JAD file was added as a new feature. Making this work required a change to the device templates used to launch emulators. This change implies the need to remove and re-import device definitions in order for the new functionality to function correctly. This detail was unfortunately not covered in the documentation. If you are encountering ClassNotFound errors, you will need to remove and re-import your device definitions in order for this new feature to function.

Recently, there have been scattered reports of problems running EclipseME on Eclipse 3.2.2 and Eclipse 3.3M5. Although there may indeed be problems with these versions, they are not readily apparent. Both 3.2.2 and 3.3M5 appear to work fine with EclipseME, at least on the surface.

As usual, if there are specific problems, they should be reported via the EclipseME Bug Tracker. If you are unsure if something is a bug or just want to talk about EclipseME, please visit the eclipseme-users mailing list. Please do not use the blog comments for support requests. Thanks.

Over the last few years, EclipseME CVS on Sourceforge has become increasingly cluttered with projects and folders that are no longer in use. This has been confusing for those that are interested in perusing the EclipseME sources. I’ve long considered switching to Subversion for EclipseME source control. The combination of these situations have finally given me enough of a push to move EclipseME over to Subversion on Sourceforge. A few details of this transition follow.

(more…)