Bug 512172 - [Tooling] Align and cleanup available UML-RT specific facet customizations in model explorer
Summary: [Tooling] Align and cleanup available UML-RT specific facet customizations in...
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: 1.0.2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2017-02-14 07:41 EST by Peter Cigehn CLA
Modified: 2017-10-17 14:35 EDT (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 Peter Cigehn CLA 2017-02-14 07:41:31 EST 
The number of UML-RT specific facet customizations are increasing, and it gets harder to understand what is what.

There are two facet customization which have rather unclear behavior and intended functionality:

simpleUMLRT (disabled by default)
UMLRTDiagrams

These should either be removed, or aligned, e.g. with respect to the usage of UML-RT with a hyphen, and possibly improve their general names.

The other (currently availble) facet customizations are:

UML-RT Inherited Structure (disabled by default)
UML-RT Inherited State Machines (disabled by default)
UML-RT Protocols
UML-RT Structure
UML-RT State Machine
Comment 1 Charles Rivet CLA 2017-02-23 11:18:28 EST 
The first step is to document these properly so we understand what each of these actually does and are they are to be used.

I would surmise that UML-RT modelers would not be concerned with these, except out of curiosity and the UML-RT toolsmiths would be aware of their used once documented as above.

There should still be a discussion re: re-architecting all of these facets (options).

Assigning to 1.0.1 for now
Comment 2 Ernesto Posse CLA 2017-10-17 14:35:35 EDT 
Mass changing all 1.0.1 bugs to target milestone 1.0.2, because Bug 520039 depends on Bug 526168 which depends on Bug 526167 which modifies plugin MANIFEST files and therefore requires a new service version number in accordance to the guidelines at https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment. Hence the solution to these bugs must be merged as a new version (1.0.1) and therefore all old 1.0.1 bugs should become 1.0.2.