Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365518 - Papyrus ModelMultiException UmlModel Path must include project and resource name: /Model
Summary: Papyrus ModelMultiException UmlModel Path must include project and resource n...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 critical with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-04 06:46 EST by Peter L Jones CLA
Modified: 2013-03-01 05:28 EST (History)
0 users

See Also:

Attachments
Stack trace (9.35 KB, text/plain)
2011-12-04 06:48 EST, Peter L Jones CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter L Jones CLA 2011-12-04 06:46:35 EST 
Build Identifier: 20110916-0149

Papyrus 0.8.2.v201111291845
EMF Common 2.7.0.v20111003-1135

On opening the diagram where a custom stereotype has been applied, the attached exception is thrown and the diagram can no longer be used - i.e. causes data loss.

(Data recovery is possible by editing the text by hand to clean it up.)


Reproducible: Always

Steps to Reproduce:
Create a Papyrus project.
Create a Papyrus Profile diagram, "Component.profile".
Create a new Stereotype "core", import "Class" from the metamodel, extend Class with core.
Save and publish.

Start a new Papyrus project.
Create a Papyrus UML diagram.
Add a Class model.
Add the standard UML profile.
Add the new Component profile.
Add a new class.
Apply the "core" stereotype.
Save and close the diagram.
Comment 1 Peter L Jones CLA 2011-12-04 06:48:06 EST 
Created attachment 207881 [details]
Stack trace
Comment 2 Peter L Jones CLA 2011-12-04 07:14:32 EST 
Just to add that applying stereotypes from registered profiles does not trigger this error (probably obvious).
Comment 3 Peter L Jones CLA 2011-12-05 10:57:10 EST 
This appears to be triggered only where there is a space in the profile pathname (not just the filename element but any path component).
Comment 4 Camille Letavernier CLA 2013-03-01 05:28:41 EST 
Fixed in r10311