Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "DSDP/MTJ/Phone Meeting 1-Mar-2006"

< DSDP‎ | MTJ
 
Line 23: Line 23:
  
 
- Mika Hoikkala provided common status of MTJ
 
- Mika Hoikkala provided common status of MTJ
 
 
:- Petri Virtanen is taking care of project management activities. Mika is actively in loop
 
:- Petri Virtanen is taking care of project management activities. Mika is actively in loop
 
:- we need to have commitment to go for summer release
 
:- we need to have commitment to go for summer release
Line 29: Line 28:
  
 
- Arto Laurila presented Nokia's implementation and architecture status
 
- Arto Laurila presented Nokia's implementation and architecture status
 
+
:- EMF models in place
- EMF models in place
+
:- runtime management work under work
 
+
:- deployement under work
- runtime management work under work
+
 
+
- deployement under work
+
 
+
  
 
- Kevin Horowitz exlained IBM status
 
- Kevin Horowitz exlained IBM status
 
+
:- basic project creation is working
- basic project creation is working
+
:- packaking tool under work, possible jad and jar can be done at the end of the week
 
+
:- Rodrigo is checking the current WSDD code and how to utilize it e.g. in Signing
- packaking tool under work, possible jad and jar can be done at the end of the week
+
:- IBM can only commit the code that comes from IBM (legal issue)
 
+
- Rodrigo is checking the current WSDD code and how to utilize it e.g. in Signing
+
 
+
- IBM can only commit the code that comes from IBM (legal issue)
+
 
+
  
 
- Craig Setera mentioned that Kevin Hunter could help in MTJ in signing
 
- Craig Setera mentioned that Kevin Hunter could help in MTJ in signing
Line 55: Line 45:
  
 
- Craig explained Antenna next steps (Kevin Hunt's project)
 
- Craig explained Antenna next steps (Kevin Hunt's project)
 
+
:- separately from EclipseME and from MTJ
- separately from EclipseME and from MTJ
+
:- could be utilized in both above
 
+
:- schedule is open
- could be utilized in both above
+
 
+
- schedule is open
+
 
+
  
 
- User documentation is more important than developer docs
 
- User documentation is more important than developer docs
 
+
:- high level, then details, troubleshooting
- high level, then details, troubleshooting
+

Latest revision as of 10:46, 13 April 2006

Meeting Title: Mobile Tools for the Java Platform Conference Call
Date & Time: Wednesday March 1, 2006 at 9am EST
US Toll free: 866-707-5108
Int'l or US Toll: +1-517-386-9625
Passcode: 6040654 #

Attendees

  • Kevin Horowitz, Rodrigo Pastrana - IBM
  • Petri Virtanen, Mika Hoikkala, Arto Laurila, Minna Bloigu - Nokia
  • Craig Setera - EclipseME

Notes

- Mika Hoikkala provided common status of MTJ

- Petri Virtanen is taking care of project management activities. Mika is actively in loop
- we need to have commitment to go for summer release
- engouraged all to participate

- Arto Laurila presented Nokia's implementation and architecture status

- EMF models in place
- runtime management work under work
- deployement under work

- Kevin Horowitz exlained IBM status

- basic project creation is working
- packaking tool under work, possible jad and jar can be done at the end of the week
- Rodrigo is checking the current WSDD code and how to utilize it e.g. in Signing
- IBM can only commit the code that comes from IBM (legal issue)

- Craig Setera mentioned that Kevin Hunter could help in MTJ in signing

- Arto proposed co-operation by changing existing code to utilize all parts as well as possible

- Arto and Kevin agreed to continue discussion related to MTJ structure in CVS and where the implementation should be done via email

- Craig explained Antenna next steps (Kevin Hunt's project)

- separately from EclipseME and from MTJ
- could be utilized in both above
- schedule is open

- User documentation is more important than developer docs

- high level, then details, troubleshooting

Back to the top