Bug 477714 - [Model Import - RT] RSARTE to Papyrus-RT model library element mapping implementation
Summary: [Model Import - RT] RSARTE to Papyrus-RT model library element mapping implem...
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.8.0   Edit
Hardware: All All
: P3 normal
Target Milestone: Future   Edit
Assignee: Charles Rivet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 477629
Blocks: 477249
  Show dependency tree
 
Reported: 2015-09-17 09:21 EDT by Charles Rivet CLA
Modified: 2017-04-05 12:24 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Rivet CLA 2015-09-17 09:21:18 EDT
Bug 477629 describes how elements from the RSARTE model library map to elements of the Papyrus-RT runtime service library and its model library.

This bug is to implement the mappings that are required as part of the model import functionality for RSARTE models.

Note that the mapping in Bug 477629 is still incomplete and still requires investigation when this bug was created.
Comment 1 Peter Cigehn CLA 2015-12-08 10:08:30 EST
Now when it is planned to move the RSARTE specific parts of the model import to the Papyrus-RT project, I guess that this Bugzilla should also be moved over to the Papyrus-RT project. I guess this Bugzilla also should be made "depends on" Bug 483828 that tracks that work.
Comment 2 Peter Cigehn CLA 2016-11-17 07:56:40 EST
Moving over to the Papyrus-RT project since the import tool has been split into a specific RSARTE import in Papyrus-RT.
Comment 3 Simon Redding CLA 2016-11-17 15:32:28 EST
Moved to 1.0. Move to future if this does not gate 1.0
Comment 4 Peter Cigehn CLA 2016-11-18 04:29:44 EST
(In reply to Simon Redding from comment #3)
> Moved to 1.0. Move to future if this does not gate 1.0

I think we have some kind of "mismatch" here. Keep in mind that this bug tracks the actual implementation of the mapping, whereas we have an "investigation" bug tracking the initial investigation about which and the mappings should be made, i.e. Bug 477629. But Bug 477629 is planned for future, so this does not match up. The split in one "investigation" and one "implementation" was initially made due to fact that the import tool was part of a Papyrus extra component, and thus we needed a separate "implementation" bug for the Papyrus project. Now when the import tool has been split in two parts, the need for tracking the "implementation" separately has been reduced.

With that said, I guess we need to plan these two bugs together, or at least plan the "investigation" bug to be done before the "implementation" bug.