Papyrus IC/Architecture/MoM/2018-01-09 Architecture Committee Minutes

Attendees

• Philip (EclipseSource)
• Rémi (chair)
• Florian (CEA)
• Ernesto (Zeligsoft)
• Antonio (Ericsson)
• Per (Saab)
• Keith (OneFact)

Next Phone call: February 6th, 2018, 4PM

Topics

UML2 And Photon

• https://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg04191.html
  • PIC Architecture Committee decided to help UML2 project staying on simrel. UML2 in Photon
  • Initial evaluation for relevant bugs from Eclipse UML2 Bugzilla with CEA - EclipseSource
    • Triage by interest: must-do / nice to have / no interest
    • File:Bugs UML2 - Photon list.pdf

Task Forces

Florian: Next year plan

• Roadmap for Photon in progress (see Photon)
• Next version: 4.0.
  • API need some major improvements
• Currently up-to-date

Philip: DSML task force

• Papyrus for information modeling used
  • blueprint for sketching and documenting how to customize papyrus
  • Papyrus-IM now migrated on Oxygen

• New Demo project for DSML support
  • more information on profile support compared to the UML reduction proposed by Papyrus-IM
  • To be published in the next months

• Antonio: tooling from Ericsson for DSML setup
  • Semi automatic generation?

Philip/Ernesto: Textual / graphical modeling

• Research project ongoing for Papyrus-RT
  • Trying to continue within next years on a European project.
  • ITEA result in January? ECSEL still ongoing

Per/Rémi: Dependency management, dependencies from Papyrus

• Remi: Currently under investigation
  • Propose a RCP with the least included features to have a working diagram
    • Rather than removing UI contributions with activities, let's not include them!
• For example: dependency from Papyrus Facet core plugin to PDE to build workspaced java based queries. That should be extracted to an other plugin to avoid pde dependency in core. Should be only proposed to toolsmith or developers.
  • Issue: API modifications for next release should be limited.
  • No tool to maintain such dependency restrictions, so hard to maintain in time. Solution should be found to help developers maintain a good architecture.

Release train for Papyrus

Oxygen

• Oxygen.2: released (End of December)
• Oxygen.3: planned for end of March 2018

Photon

• M1 - M4 already done
• M5: Beginning of February 2018

Additional topics

• Stability in Papyrus?
  • Breaking APIs: migration of models between Neon and Oxygen due to Architecture description introduction & some issues with tables
    • Steering committee to answer on that trade off?
  • https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15023.html
    • More frequent release of the Eclipse SDK
    • What about Papyrus (and its dependencies?)?