Bugzilla – Full Text Bug Listing
| Summary: | Classes from dependent module are not deleted automatically from diagrams when dependency removed | ||
|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Yossi Shmulevitch <yshmulev> |
| Component: | Diagrams | Assignee: | Project Inbox <tigerstripe.diagram-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | nmehrega |
| Version: | unspecified | ||
| Target Milestone: | 0.5M0 | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Yossi Shmulevitch
Copy/Pasting e-mail that was sent earlier: I don't agree with automatically deleting the artifacts from class diagrams once project references are modified. Users should be notified of such inconsistencies as opposed to having artifacts magically disappearing from their diagrams. Now, one thing to keep in mind is that generation is done on the model artifacts and not on class diagrams. Class diagrams are just a way of organizing your model artifacts visually. They don't play a role when it comes to generation. When you have an Association from your model artifact to a "dangling" artifact, it's the Association artifact that goes into error, not the class diagram. In fact, error markers are not associated with class diagrams at all. Due to the size of our diagrams, it would be way too inefficient to run automatic auditors on diagrams. This is why we have the 'Audit Diagram' action. If you right click on your model project > select Diagrams > Audit All Diagrams, the tool will automatically capture this and all other inconsistencies with your diagram (see attached snapshot). I've already tried your scenario and it's correctly captured as an inconsistency. IMO, we don't need to make any changes. The 'Audit Diagram' action will automatically capture such inconsistencies. Please reopen defect if you disagree. |