Community
Participate
Working Groups
Investigate and identify required mappings between CppPropertySets profile and RTCppProperties profile.
Closed - profiles and property sets have changed extensively since this bug was created.
(In reply to Charles Rivet from comment #1) > Closed - profiles and property sets have changed extensively since this bug > was created. I am not sure I understand the reason for closing this one as WONTFIX? Since this is the Bugzilla tracking the investigations regarding which mappings shall be done, it does not really matter that the RtCppProperties profile have changed since this Bugzilla was written (that is what the investigation is all about, i.e. to conclude how the mapping shall be done). Will a new one be written to track this instead? This investigation Bugzilla still blocks Bug 479176, which is tracking the actual implementation of the mappings in the import tool. As I see it, this Bug 479240 for the investigation and its implementation Bug 479176, is following the same structure we have for Bug 477629 for the investigation and its related implementation in Bug 477714. If we do not plan on having this structure of one investigation and one implementation Bugzilla for both these two major areas regarding import of legacy models, then I suggest that we are consistent and close the other investigation Bug 477629 as well (or keep both open).
(In reply to Peter Cigehn from comment #2) > (In reply to Charles Rivet from comment #1) > > Closed - profiles and property sets have changed extensively since this bug > > was created. > > I am not sure I understand the reason for closing this one as WONTFIX? Since > this is the Bugzilla tracking the investigations regarding which mappings > shall be done, it does not really matter that the RtCppProperties profile > have changed since this Bugzilla was written (that is what the investigation > is all about, i.e. to conclude how the mapping shall be done). > > Will a new one be written to track this instead? This investigation Bugzilla > still blocks Bug 479176, which is tracking the actual implementation of the > mappings in the import tool. > > As I see it, this Bug 479240 for the investigation and its implementation > Bug 479176, is following the same structure we have for Bug 477629 for the > investigation and its related implementation in Bug 477714. > > If we do not plan on having this structure of one investigation and one > implementation Bugzilla for both these two major areas regarding import of > legacy models, then I suggest that we are consistent and close the other > investigation Bug 477629 as well (or keep both open). Agreed, missed the relationship to the Papyrus bug. Moved to future until determination of migration importance in the release planning.
(In reply to Charles Rivet from comment #3) > Agreed, missed the relationship to the Papyrus bug. Just to be clear: Bug 479176 should really be moved over to Papyrus-RT (now when the import tool has been splitted in two parts, one for RSA in Papyrus, and one for RSARTE in Papyrus-RT). I have proposed this in Bug 479176 Comment 5, but no one has so far done so. Actually Bug 477714 should also be moved over to Papyrus-RT for the same reason, see Bug 477714 Comment 2.
Both bugs mentionned by Peter (Bug 477714 & Bug 479176) have been moved to Papyrus-RT, but the planning seems not coherent, with bug for 1.0.0 or 0.9.0 depending on 'Future' bugs.
(In reply to Remi Schnekenburger from comment #5) > Both bugs mentionned by Peter (Bug 477714 & Bug 479176) have been moved to > Papyrus-RT, but the planning seems not coherent, with bug for 1.0.0 or 0.9.0 > depending on 'Future' bugs. Correct, as I already commented on in Bug 477714 Comment 4 we need to plan these two pairs of "investigation" and "implementation" bugs together. If this is hard to keep track of (which it seem to be), then maybe we can combine the "investigation" bug and the "implementation" bug and only have one for the run-time model library mappings respectively one for the C++ property sets mapping, now when they all are assigned to Papyrus-RT anyway.
