| Summary: | [Papyrus preferences] add a model repository pathmap in the preference | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Patrick Tessier <Patrick.Tessier> |
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | BobFieldsFB, papyrus-bugs, ronan.barrett, rschnekenburger, toni.siljamaki |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Patrick Tessier
I was the on who asked the original question on the newsgroup, see http://www.eclipse.org/forums/index.php?t=rview&goto=640626. I haven't tested this yet, but I assume it is also possible to select a package within an existing Papyrus model, and make that into an external model, with all cross-model references intact? Or to create a new model and move elements between the models (graphically?). That will be necessary when maintaining very large models on an ongoing basis. I don't think this is an issue anymore. We have model/profile import now. Pathmaps also work as they should. Can we close this? Yes, we can close. model libraries can be imported, and the control mode allows to split the model in several fils. closing bug Have this been verified wrt: 1) profile applications in fragments/controlled parts? 2) ...and the diagrams? 3) ...and with profile applications in separate files? (the new feature) |