Bugzilla – Full Text Bug Listing
| Summary: | [Model Import - RT] Update the Model Import to target Papyrus-RT | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Camille Letavernier <cletavernier> |
| Component: | Others | Assignee: | Camille Letavernier <cletavernier> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | papyrus-bugs, peter.cigehn, rschnekenburger |
| Version: | 1.1.0 | ||
| Target Milestone: | SR1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 467520 | ||
| Bug Blocks: | 467518 | ||
|
Description
Camille Letavernier
Done in fe00f9c on master Waiting for the final version of PapyrusRT 0.7.0 before porting the change to Mars SR1, to avoid any update issue between 0.7.0"a" and 0.7.0"b" We should also include PapyrusRT.profile to the Model Import feature, so that users don't have to manually set up the PapyrusRT update site (Which is not present in the release train) > We should also include PapyrusRT.profile to the Model Import feature, so that users don't have to manually set up the PapyrusRT update site (Which is not present in the release train)
The plug-in is now included in the Model Import feature (6f7130b)
Both commits have been backported to Mars for SR1 (62e253d, aff4fde)
> We should also include PapyrusRT.profile to the Model Import feature, so that users don't have to manually set up the PapyrusRT update site (Which is not present in the release train)
This approach unfortunately causes update issues, since the UML-RT Profile plug-in is not a singleton. If several features provide the same plug-in with different versions, it won't be possible to install them together.
Instead of shipping the plug-in with the feature, I'll try to include it in the update site (So that Eclipse can find it when required, but doesn't force installation of this specific version if any newer version is available)
I pushed a partial solution (Mars only for now; I'll port it to master if it is satisfying) for including the PapyrusRT Profile in the update site rather than in the Model Import feature. Commit 1857a1f on Mars I've tested to install the RSA import tool on top of my nightly build installation of Papyrus-RT, and indeed it now works. No conflicts, and the RSA import tools seem to have installed correctly. I made a quick import of a small example model I have made for testing the code-generator/run-time and it did import without any obvious errors (only the expected "UML-RT language installation not implemented" error was logged). So it looks like it works. Now I will be able to test the import a bit more in the context of the latest Papyrus-RT tooling. One thing that I have been suspicious about is the specific capsule composite structure diagram, and indeed when opening the imported model, the composite structure diagrams are the "standard" ones and none of the UML-RT specific tools are available on the palette. But this I guess is a completely separate issue. I just wanted to mention it... :) > One thing that I have been suspicious about is the specific capsule composite structure diagram, and indeed when opening the imported model, the composite structure diagrams are the "standard" ones and none of the UML-RT specific tools are available on the palette. But this I guess is a completely separate issue. I just wanted to mention it... :)
Indeed, there is still no specific support for RT Diagrams. In Papyrus, the modification is trivial; I'm not sure for RSA.
> I pushed a partial solution (Mars only for now; I'll port it to master if it is satisfying) for including the PapyrusRT Profile in the update site rather than in the Model Import feature.
>
> Commit 1857a1f on Mars
The fix has now been applied on master as well (commit 5368c63)
|