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: | Documentation on a diagram is lost once the diagram is closed | ||
---|---|---|---|
Product: | uml | Reporter: | ieising <ieising> |
Component: | Diagram Activity | Assignee: | issues@uml <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows Vista | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
ieising
2009-03-25 12:09:27 UTC
just tried with current version and it works, what nb build do you use? was diagram marked as dirty after entering documantation, did you save it when close? I'm using dev build 2003032241535. No, the diagram wasn't marked dirty after adding the documentation. When I add the documentation to the activity of the diagram itself (so in the project view select the activity that would open the diagram) the documentation stays with the activity. Iwan Additionally good to know, the UML project was started using NB 6.5 Iwan do you mean you open uml project created in 6.5 or install dev uml plugin on top of netbeans 6.5 or somehow else mix installations? can you reproduce the issue and attach message log or/and sample project? also does "click on the diagram itself" means click in empty space in diagram editor? The project I'm working on is started using NB65 but because of this issue, I opened it in this dev build. I'll install a virging copy of NB67 dev 200303241535 with new userdir as well and not importing any settings. Iwan Ok, this now works... only in this dev build the generate report crashes. I've submitted the issue thru NB's mechanics to do so. Iwan FYI: When I open the diagrams in NB65 again, after I've verified that it works correctly in NB67 dev build 200303241535, the documentation is gone again. Iwan there is an issue with documentation in 6.5 it's fixed in 6.7 and was expected to be in patch for 6.5 but somehow patch process fails. *** This issue has been marked as a duplicate of 154629 *** |