Community
Participate
Working Groups
It could be interested to put a pathmap for repository of model or profiles in order to find directly element from import profile or apply profile. I included the note from the newsgroup: I also wanted to import an existing profile from the file system (profile does not exist in the workspace). We use maven and source control to update our profiles, and want to reference them in the model by pathmap, something like pathmap://M2_REPO/profileLocation. I can only import profiles that have been deployed to Eclipse or that exist in the workspace. I would want to select a profile from the file system and have Papyrus recognize that the directory location corresponds to an existing PATHMAP value (in preferences) and use that pathmap variable.
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)
