VIATRA/DeveloperMeetingMinutes/Meeting20181018

Topics

• Current status: Bugzilla Gerrit AERI
• Release status
  • VIATRA 2.1.0 M3 on 17th October
• What to do with MoDisco integration?
  • Limited uses
  • https://www.eclipse.org/lists/viatra-dev/msg00840.html
• Problems with generics in transformation API
  • https://bugs.eclipse.org/bugs/show_bug.cgi?id=539915
  • http://git.eclipse.org/c/viatra/org.eclipse.viatra.git/commit/?id=d05566e2707ac727bfa6f88e2eb1c11b42399e33
  • Question: do we want to “change” the API or only provide an alternative?
• Concurrent modification exception

Minutes

• M3 contributed to 2018-12
  • 2 more 3-week feature cycles before RC phase
  • 2.0.3 planned with a few bug fixes already marked for backporting
• MoDisco integration will be removed as there are no known users
• Generics in xform rule builder

N** ew create method and constructor added as short term workaround

• • Decision: deprecate old method and constructor
• Concurrent modification exception
  • Thrown when metamodel is only in target platform and there is a race condition with target platform updating
  • Workarounds:
    • Install metamodel in host
    • Enable experimental target platform caching
    • Disable Manifest.mf and plugin.xml generation
  • No easy solution (internal Xtext and PDE behavior would need to be changed)
    • PDE: not thread-safe plugin model retrieval
    • Xtext: no way to control when it triggers target platform update
• Merging tooling.ui plugins (emf.ui, tooling.ui, tooling.ui.browser, migrator)
• New runtime.ui plugin to contain IModelConnector
  • Sphinx: Balázs will look at Sphinx usage