Bug 527278 - Control our build-dependency on UML2
Summary: Control our build-dependency on UML2
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-11-15 02:40 EST by Pierre-Charles David CLA
Modified: 2017-11-17 04:50 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Charles David CLA 2017-11-15 02:40:19 EST 
Currently we use a single global Target Platform definition to build both Sirius and our tests. Some of our tests use UML2 models, so UML2 is present in that Target Platform. The future of UML2 is currently uncertain (see https://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg04191.html), and we can't take the risk of being unable to build Sirius itself if UML2 becomes unavailable at some point (or at least not part of the train anymore).

This may resolve itself without any action on our part if the situation evolves on the UML2 side, and it's probably not a large change for us (we used to have separate TPs and build for the core and tests), but we should be ready to change our builds if needed.

A possible option is to get UML2 from a fixed repository from the project itself instead of from the SimRel repo of each target we support. We'll need to synchronize with Mélanie and the UML Designer team to make sure we use the same version. Dropping UML from our tests completely does not seem like an option: given its relatively wide usage in practice we must ensure Sirius works well with it.