logoTop pad
Table of Contents
Creating a new project
Creating a new MIDlet
Packaging for deployment
For EclipseME developers

Eclipse Ready Logo
SourceForge.net Logo

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 1.5.0

Migration to version 1.5.0 from previous versions requires manual intervention. See 1.5.0 migration instructions for full information on the transition.

Migrate to Version 1.2.3

Migration to version 1.2.3 is automatic. To make sure that your projects are appropriately migrated, follow these steps:

  1. Open all EclipseME J2ME projects that you would like to have migrated.
  2. Exit Eclipse.
  3. Update EclipseME using the update instructions.
  4. Start Eclipse.
  5. Allow Eclipse to completely start.
  6. Exit Eclipse.

Migrating to Version 1.0.0

Migration to version 1.0.0 from versions 0.9.4 and later is automatic.

Migrating to Version 0.9.4

For many users, migration to version 0.9.4 from versions 0.5.0 and later is automatic. Version 0.9.4, however, contains a change that may cause some problems with users who have multiple EclipseME projects that connect together.

"Breaking Change" - Export Settings of Java Build Path are now honored


Previously, if your EclipseME project had an external jar imported into it, or had another EclipseME project listed as a prerequisite project, the builder would recursively follow those references. For each of those references, the contents of the jar or compiled output would be preverified into the "verified" folder of the current project. The verified resources were all included into the deployed package when it is built. Finally, for Ant users, the generated Ant build scripts would be generated to include the same resources that would be built by EclipseME.

Technically, this behavior was not in accordance with Eclipse standards. In particular, according to Eclipse standards, only those items that are "exported" from a project should be included into other projects that make this project a prerequisite. This allows, for example, a project to include unit test code or other resources that are used internally, but which don't belong in other projects that use this one.

In order to export resources from a project, one uses the "Order and Export" tab in the "Java Build Path" portion of the project properties.

In this simple project, the "MyMidlet/src" item is checked. As a result, all of the resources in the "src" tree of this particular project will be verified and copied into any other project that makes this a prerequisite.

Consider a more complicated project, however, that includes an external jar file. In this example, the jar file is located within the project file area, however it could be external as well. In either case, it has been included in the project by adding it to the "Libraries" tab of the "Java Build Path" portion of the project properties.

By default, however, when a jar is added to the project, it is not automatically included in the items exported from the project, as shown below.

Before Version 0.9.4, all the resources in "mmapi.jar" would have been preverified and included into both the "MyMidlet" project and also into any project that was dependent on this project.

After the changes, the "export" checkbox in the Java Build Path dialog will now be honored. That means that jar files or prerequisite projects that have not been selected for export will not be preverified, nor will they be included in a deployed jar file. They also will not be included into other projects dependent on this one. Finally, the exported Ant build files are set up to honor the export settings.

What does this mean to you?

  • If your EclipseME project(s) do not include external jar files that need to be packaged as part of your deployed jar file, and do not use dependent projects, this change will not affect you, and you do not need to make any changes.
  • If your EclipseME project includes an external jar file that does need to be included as part of your deployed jar file, you must now check the "export" box next to that jar file on the "Exports and Order" tab in the project properties. If you fail to do this, the contents of the jar file will not be preverified and deployed.
  • If your EclipseME project includes another Eclipse project as a dependent project, you must verify that the correct items are exported in the dependent project.

The EclipseME developers regret that this change will cause some migration issues for certain users, however it was felt that getting the EclipseME behavior "correct" for the future was worth the temporary hassles this will cause to pre-0.9.4 users who are using external jars and dependent projects. In particular, properly honoring these settings makes it substantially easier for users who are including "extra" jar files that are intended to more fully simulate the environment on a particular device.

Migrating to Version 0.9.2

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

Migrating to Version 0.9.0

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

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:

  • You can move the resources that you want included to your existing source folder(s).
  • You can designate your resources directory as an additional source folder. The steps to create an additional source folder are described in the FAQ.

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.


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.

Copyright © 2005, http://www.eclipseme.org. All rights reserved.