This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | package stereotype value removed after being moved to another model project | ||
---|---|---|---|
Product: | uml | Reporter: | Joanne Lau <j_lau> |
Component: | Diagram Class | Assignee: | issues@uml <issues> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
package with stereotype and tag value shown in proj1
package moved to Proj2, stereotype value is lost package shown in proj1 after being moved to proj2, stereotype shown |
Description
Joanne Lau
2008-06-23 20:33:01 UTC
Created attachment 63291 [details]
package with stereotype and tag value shown in proj1
Created attachment 63292 [details]
package moved to Proj2, stereotype value is lost
Created attachment 63293 [details]
package shown in proj1 after being moved to proj2, stereotype shown
This is not a persistence issue.. it happens when you drag the package from one project to another. It looks like this was fixed by sheryls import element changes. I was not able to reproduce this problem. fixed verified in build 20080725. If I just import it by answering No to the dialog, the stereotype is still there. If I move the package to another project by answering Yes to the dialog, the stereotype is lost. When adding a stereotype to an element, a stereo type model element is created under project namespace 'Profile', it is meant to stay in the original project as it could be reused by other model elements. This is why the moved element does not show the stereotype as it was defined in another project. Since uml profile itself is not a fully supported feature in the tool, moving an element from one project to another is an uncommon scenario, this issue has very little impact on users, p4 would be more appropriate. |