DSDP/MTJ/Face-to-Face Meeting Boca Raton 8-Dec-2005

From Eclipsepedia

< DSDP‎ | MTJ
Revision as of 03:13, 13 April 2006 by Pvirtanen (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

-- Attendees --

  • Hoikkala Mika, Laurila Arto - Nokia
  • Reich David, Kevin Horowitz - IBM
  • Craig Setera - EclipseME
  • Fernando Concha - Sony Ericsson

-- Notes -- Agreed project schedule:

   * 1st internal milestone: 27th Jan 2006
   * 2nd internal milestone: 31th March 2006
   * 3rd internal milestone: 28th April 2006
   *
     Release date: 28th June 2006

3rd internal milestone will also be milestone for "feature complete".

Last month is reserved for bug fixing and testing. Core content of the 1st internal milestone:

   * UC: Create project (Kevin Horowitz, IBM)
   * UC: Packaging (Kevin will inform Mika when things are done)
   * UC: Partially, to be able to deploy one environment, even manually is OK (Mika to discuss with Arto and Petri Virtanen)
   * UC: Partially, Manage runtime, Get SDK to attached (Mika to discuss with Arto and Petri)
   * MTJ plug-in. Core for "frameworks". Common way to extend and use Eclipse plug-ins.

Next steps in 1st iteration: Create project

   * Finalize use cases, do design, implementation and testing
   * Kevin to inform Mika when things are done (i.e short plan)

Packaging

   * Finalize use cases, do design, implementation and testing
   * Kevin to inform Mika when things are done (i.e short plan)

Deployment

   * Minumum requirement is that output can be manually deployed to at least one environment
   * Mika to discuss with Arto Laurila and Petri Virtanen what to actually implement

Runtime Management, Get SDKs to attached

   * Finalize use cases, do design, implementation and testing
   * Mika to discuss with Arto Laurila and Petri Virtanen what to actually implement

Status of code contributions:

IBM: Almost ready. Last things processed with layers. Finalized probably in next few days.

Although code is already Eclipse code there are bunch of things that should be changed (like J9 dependencies)

Nokia: Almost ready. Last things processed with layers. Finalized probably in next few days.

Current "NDS for J2ME" code is generic code which can be integrated to Eclipse, Netbeans and other environments. Don't work as such in Eclipse.

EclipseME: Agreed. Craig and Kevin from EclipseME are willing to contribute components.

(potential discussed components were preverifier and preprosessing (for future device fragmentation solution)) Misc topics:

Focus of MTJ should be to support all the J2ME environments and it should support scenarios where developer targets to multiple targets or only one target device.

One core feature in Eclipse is incremental building which also MTJ should utilize and not only use for example ANT based building. MTJ should also try to do optimizations so that whole JAR file don't have to be recreated if only one resource inside needed update.

Arto Laurila, Craig Setera and Kevin Horowitz will work during week 51 to verify that code contributor can access CVS and development can start.

Package name for MTJ is: org.eclipse.mtj

New contributors for MTJ should start by participating to testing and documentation. This is also good way to learn what MTJ is.

MTJ needs some graphics. Nokia and IBM will check what we can get.

One things what should be studied in MTJ is that how to discover installed SDK automatically. Intial code contributors are:

   * Arto Laurila
   * Marius Voicu
   * Minna Bloigu
   * Kevin Horowitz
   * David Reich
   * Fernando Concha

Intial list of MTJ components:

Components & subsystems:

   * Project creation
   * Packaging
   * Editor framework -> most likely nothing
   * JAD editor
   * Signing Tools (Key management, signing)
   * Obfuscation
   * Preverifier
   * Emulator FW
   * Deploy FW
   * Emulator run
   * Emulator debug
   * Refactoring (fix JAD file if class name changes)

Roles in MTJ:

Project Manager: Mika Hoikkala

Lead developer: Mika and David to discuss

Architecture: Arto, David and Craig Setera

Test Plan: David Reich

component lead is responsible of testing, developer shouldn't be the only tester, Junit test cases should be included with the code, NOTE: there is component + plug-in level testing

Documentation:

how to handle testing, component leads are responsible to product raw material. Mika to check if Nokia could provide. Also we should check how community can help us. technical writers to make clear documents for end users.

Building management: Arto Laurila. David to provide one person to participate, Craig will also provide help