| Summary: | [Tooling] Renaming a protocol using F2 only renames the internal collaboration | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus-rt | Reporter: | Peter Cigehn <peter.cigehn> |
| Component: | tool | Assignee: | Christian Damus <give.a.damus> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | charles, papyrus-bugs |
| Version: | 0.7.2 | ||
| Target Milestone: | 0.9.0 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=492356 | ||
| Whiteboard: | |||
| Bug Depends on: | 506896 | ||
| Bug Blocks: | |||
|
Description
Peter Cigehn
The fix for blocking bug 506895 is available in the latest Papyrus Neon.2 nightly builds. I have verified this in the latest Papyrus-RT build. All the internal elements of the protocol (<<ProtocolContainer>> Package, <<Protocol>> Collaboration and the three <<RTMessageSet>> Interfaces) gets renamed according to their naming rules when using F2. Closing as verified fixed. |