Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
E4/Scripting/telcon20130904
Contents
Attendees
- Arthur Daussy, ATOS
- Christian Pontesegger, Infineon
- Martin Oberhuber, WindRiver
Agenda
The aim of this meeting was to discuss technical solution for the new eclipse project. Agenda :
- Eclipse Monkey Revival Vs EScript
- Make choice about language syntax
- Team Organization
- Deadlines
Choices
- Technical choices
- The EScript project will be use a base. Cause
- The project is more recent
- The architecture is more clear and quite close the Eclipse Monkey one( Not difficult to integrate Eclipse Monkey contribution)
- Eclipse Monkey contribution to migrate to new project
- Script Tree view
- Script Menu
- Metadatas
- Some work on python
- Migrate DOMs into modules. The module will now be loaded thanks to the loadModule instruction or statically thanks to the metadata.
- The EScript project will be use a base. Cause
- A new reposoritory will be created on github waiting for integration in eclipse. First committers :
- Christian Pontesegger, Infineon
- Martin Oberhuber, WindRiver
- Arthur Daussy, ATOS
- A new reposoritory will be created on github waiting for integration in eclipse. First committers :
- Deadlines
- Aim to make write the proposal before the end of september
- Deadlines
Tasks
- Arthur
- Create a new repo
- Change namespace to be Eclipse compliant
- Migrate Eclipse Monkey contribution + samples
- Work to make python work
- Migrate Topcased Dom
- Christan
- Integrat current work (debugger etc...)
- Make maven build work in new space
- Martin
- Look for correct Eclipse Architecture of builds
- Open task
- Find a way to integrate Jython,JRuby and groovy into eclipse fondation
Nex meetings
- 09/06/2013 11 am to discuss module mechanism
- 09/11/2013 11 am to discuss project progress