Migration from Previous Versions

This page provides information that is helpful when migrating from earlier version of EclipseME. These migration steps are done automatically by EclipseME, unless otherwise noted.

Migrating to Version 0.7.5

Migration to version 0.7.5 from versions 0.5.0 and later is automatic.

Note that automatic support for migration from releases before 0.5.0 has been removed. Users of earlier versions who are updating to 0.7.5 or later must migrate manually.

Migrating to Version 0.7.0

Migration to version 0.7.0 is automatic. Note that the addition of MIDlet signing to version 0.7.0 has changed the format of the EclipseME metadata. Thus, projects that are migrated to 0.7.0 will not be backwards compatible to 0.6.1 and earlier.

Migrating to Version 0.6.1

Migration to version 0.6.1 is automatic.

Migrating to Version 0.6.0

Migration to version 0.6.0 is automatic.

Migrating to Version 0.5.5

Migrating to version 0.5.5 is mostly automatic, with one exception:

As a result of RFE 1001717, the "Resources" directory that used to be specified on the Basic J2ME Preferences page has been removed. If you previously used a resource directory specified in this manner to have images, etc. included into your deployed build, you have two choices:

Migrating to Version 0.5.0

Migration to version 0.5.0 is mostly automatic, but a few steps need to be taken to help the process along.

  1. Shutdown Eclipse
  2. Remove the currently installed EclipseME plugin.
  3. Unzip version 0.5.0 to your Eclipse installation directory. The zip file should be unzipped into the root Eclipse directory rather than the plugins directory.
  4. Restart Eclipse
  5. Do Project -> Clean... All

The last step is very important. Much of the migration is done during the process of the first build of each project. Make sure that all EclipseME projects are open before doing the clean operation. During this migration, each project's ".project" and ".classpath" files will be updated to match the new structure of the plugin. These files should be saved to source control as normal.

For further installation information, refer to the installation instructions.

Migrating to Version 0.4.5

No migration necessary.

Migrating to Version 0.4.0

No migration necessary.

Migrating to Version 0.3.5

No migration necessary.

Migrating to Version 0.3.0

Platform Components View is now in J2ME Preferences

In version 0.3.0 of EclipseME, the function of the Platform Components view has been moved to a J2ME preference page. This will cause errors while opening perspectives that contain the Platform Components View. It is expected that you will see an error about the workbench being unable to restore the workbench layout. Selecting "OK" at this point will restore the perspective without the Platform Components view. This error will only occur once.

To avoid this error at all, close the Platform Components view before updating to EclipseME 0.3.0.

Platform Definition Storage

In previous versions of EclipseME, the platform definition was stored in a per-project persistent property. This property could not be stored to source control or moved to another machine. In this version, if the property is found on the project, it will be automatically migrated to the file ".eclipseme" within the project. This file may be persisted to source control or moved to another machine without any trouble.

Migrating from Classpath Variables to Classpath Containers

In previous versions of EclipseME, platform libraries were represented by individual library entries in the build path of each midlet suite. These entries were generally based on classpath variables defined by each wireless toolkit and were difficult to change after the project was created.

This release introduces classpath containers as the mechanism to store the build path libraries that are derived from the selected platform definition. In the following snapshot, the Midlet Suite is currently associated with the Sony Ericsson MIDP 1.0 platform definition.

screenshot

The first time that the Midlet Suite's Platform Definition is altered via the Project J2ME Properties, EclipseME will create the necessary classpath container within the Midlet Suite project. Any individual classpath entries that exist in the project and are part of the platform definition will be removed at that time. It is quite possible that some individual entries may still exist after this migration. Those entries should be manually removed to avoid any future problems.

Migrating to Version 0.1.0

JAD files were created using the wrong format in previous versions of EclipseME. Version 0.1.0 corrects this formatting and migrates JAD files found in Midlet Suite projects to the correct formatting.