Jump to: navigation, search

DSDP/MTJ/Discussion/Requirements

< DSDP‎ | MTJ‎ | Discussion
Revision as of 12:36, 28 May 2008 by Wgp010.motorola.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Below is a list of requirements that are supported on current MTJ. This list is based on what is currently supported on EclipseME. It is necessary to discuss if we need to add/change/remove some of those requirements on MTJ. Those requirements are formally listed on the MTJ Requirements Document.

Feel free to add comments to each of those requirements in a separated wiki page.


  • MTJ shall provide support to MIDP/IMP Profiles
  • MTJ shall provide support to CLDC
  • MTJ shall be platform independent and runs on all OSs that Eclipse can be executed
  • MTJ shall depend on Eclipse Platform/JDT 3.3.X and Eclipse Platform/JDT 3.4.Y

  • MTJ shall provide a wizard to create a MIDlet Suite as an Eclipse Project
  • MTJ shall provide a wizard to create a MIDlet Class
  • MTJ shall provide a Java Application Descriptor (JAD) Editor
  • MTJ shall provide a preferences page for each MTJ Project
  • MTJ shall provide a general preferences page on Eclipse Preferences
  • MTJ shall provide a way to change the current MTJ project target SDK and Device
  • MTJ shall execute a MIDlet suite based on its JAD file
  • MTJ shall execute a MIDlet suite based on the MIDlet Class
  • MTJ shall execute a MIDlet suite over the air (install the suite on the SDK)

  • MTJ shall provide a MIDP Packing Build Process
  • MTJ shall provide a built-in CLDC 1.1 compliant preferifier
  • MTJ shall provide an option to setup proguard code obfuscation
  • MTJ shall provide an option to setup a signing keystore
  • MTJ shall provide an option to build the MIDlet Suite JAR without obfuscation
  • MTJ shall provide an option to build an obfuscated MIDlet Suite JAR
  • MTJ shall provide an option to export all build process an an antenna build XML file

MTJ shall be able to import a MIDP SDK MTJ shall be extendible to add new import SDKs mechanisms MTJ shall support UEI Compliant SDKs MTJ shall support Non-UEI Compliant SDKs (100% java SDKs) MTJ shall be able to remove one specific device of each SDK MTJ shall be able to edit one specific device of each SDK