Project Plan For Mobile Tools for Java, version 1.1

Introduction

The goal of the Mobile Tools for Java TM (MTJ) project is to extend existing Eclipse frameworks to support mobile device Java application development. MTJ will enable developers to develop, debug and deploy Mobile Java applications to emulators and real devices. The base code of MTJ is EclipseME version 1.7.9.

Last year DSDP MTJ was part of the Galileo train and it was also included in the Eclipse Pulsar Package. Most of the features requested by the users are already implemented.

Next MTJ release will be part of Helios Train. The main focus of this release is bug fixes. The plan is to address as much as possible all issues that are raised from the community after the 1.0 release. Besides that, there are some external contributions that will also be available, and some issues on the API that need to be fixed. Eclipse Pulsar related features also need to be removed from MTJ, since they were moved to Eclipse Sechoya project

DSDP 1.1 scope is listed below

  • Fix major bugs of MTJ 1.0.X,
  • Support new external components (antenna preprocessor and jetty),
  • SDKImporter API (RIM contributed),
  • Remove Eclipse Pulsar Features,
  • small API fixes.

Release Deliverables

There are three main deliverables on DADP Mobile Tools for Java project:

  • MTJ SDK that includes all binaries and source files,
  • MTJ Runtime that includes only the binaries,
  • MTJ Examples that includes examples of how to use each of MTJ APIs.

The source code repository is available at the MTJ SVN Repository.

Table of Contents

Release Milestones

Below is a list of all milestones of this release. Those dates care aligned with Eclipse Helios Train milestones dates. MTJ is integrated on the train with a +1 offset of each milestone. One important aspect is that there were no MTJ builds during the beginning of the train. Those builds will start to be produced from M7 on. Since that only those dates are presented below
M73/5/201
1.1 M7
RC117/5/2010
1.1 RC1 (Bug Fixes)
RC224/5/2010
1.1 RC2 (Documentation and major bug fixes Only)
RC331/5/2010
1.1 RC3 (Documentation and major bug fixes Only)
RC47/6/2010
1.1 RC4
GA23/6/2010
1.1 GA

Table of Contents

Target Environments

MTJ Deliverables will be tested on the following platforms. Those tests depend on community effort contribution

Mobile Tools for Java Reference Platforms
Operating system OS version Processor architecture Window system Java 2 Platform JavaME SDK
Microsoft Windows XP x86 Win32 Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows MOTODEV SDK for JavaME 1.3
Microsoft Windows XP x86 Win32 Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows Sun Java Wireless Toolkit 2.5.2 for CLDC
Microsoft Windows XP x86 Win32 Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows Nokia Series 40 Developer Platform 2.0 SDK
Red Hat Enterprise Linux WS 4 update 2 x86 GTK Sun Java 2 Standard Edition 5.0 Update 14 for Linux x86 Sun Java Wireless Toolkit 2.5.2 for CLDC
Apple Mac OS X 10.5 x86 Carbon Apple Java 2 Platform Standard Edition (J2SE) 5, service release 4 Mpowerplayer build 1185
Apple Mac OS X 10.5 x86 Carbon Apple Java 2 Platform Standard Edition (J2SE) 5, service release 4 Microemu 2.0.3

Although untested, MTJ should work fine on other OSes that support the same window system. For Win32: NT, 2000, Vista, and Server 2003; SWT HTML viewer requires Internet Explorer 5 (or higher). For GTK on other Linux systems: version 2.2.1 of the GTK+ widget toolkit and associated libraries (GLib, Pango).

Internationalization

DSDT Mobile Tools for Java is completely preparaded to be used by localized products. All of its UI components have externalized strings. English is provided as the default language, but MTJ is part of Eclipse Babel and the community helps to generate other translations.

Table of Contents

Compatibility with Previous Releases

In terms of compatibility, there are three main aspects that need to be considered.

API Contract Compatibility: MTJ API will keep the contract compatibility on 1.0.X release. There are only two small issues that will be fixed

SDK Workspace format compatibility: Currently there is no plan to change the format that the imported SDKs are stored.

MIDlet Workspace format compatibility: Currently there is no plan to change the MIDlet project format on the 1.1 release.

Table of Contents

Themes and Priorities

Plan items listed below are based on the original planning objectives that were established on the Mobile Tools for Java Project 1.1.

Fix and Improve

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"