| Summary: | [modeling] Ecore class added to context without interaction | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Benjamin Muskalla <b.muskalla> |
| Component: | Mylyn | Assignee: | Miles Parker <milesparker> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | milesparker |
| Version: | unspecified | ||
| Target Milestone: | 0.9 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 354787 | ||
|
Description
Benjamin Muskalla
Same happens with Papurys: * several model files in one papyrus project * new task, open one model (context is ok) * add a new class, model.notation and model.uml are added to context (wrong) * another model (in my case model2.di) is added to the context (wrong) I can't replicate so I assume that it must have been fixed along the way. Oh sorry. This was with Ecore diagram. Not sure about Papyrus, see previous bug 354569 for details. OK, this looks to be fixxed. Only the actual uml object is added. |