Community
Participate
Working Groups
Build Identifier: 3.6.1.r361_v20100909 If some entities or other artifacts are imported to a diagrams of a model project , and those artifacts are part of a referenced project, those artifacts will stay at the diagrams after the removal of the dependent module. System details: eclipse.commands=-os macosx -ws cocoa -arch x86_64 -showsplash -launcher ... -name ... --launcher.library /Applications/Surf/XMP-SDK-Time-Turner-Aug-24.app/Contents/Profile/xmp_sdk.app/Contents/MacOS//../../../../../../Common/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.1.R36x_v20100810/eclipse_1309.so -startup /Applications/Surf/XMP-SDK-Time-Turner-Aug-24.app/Contents/Profile/xmp_sdk.app/Contents/MacOS/../../../../../../Common/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -install .... -vm /System/Library/Frameworks/JavaVM.framework eclipse.launcher.name=Xmp_sdk eclipse.p2.data.area=file:/Applications/Surf/Common/configuration/ eclipse.p2.profile=com.poweredbypulse.profile-4820-rmb-23658 eclipse.product=com.cisco.xmp.sdk.welcome.product eclipse.startTime=1314336818864 eclipse.vm=/System/Library/Frameworks/JavaVM.framework eclipse.vmargs=-Xms100m -Xmx1000m -Dorg.eclipse.swt.internal.carbon.smallFonts -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=256m uinox.launcher_1.1.0.v20100507.jar equinox.use.ds=true file.encoding=MacRoman file.encoding.pkg=sun.io file.separator=/ gopherProxySet=false guice.disable.misplaced.annotation.check=true java.awt.graphicsenv=apple.awt.CGraphicsEnvironment java.awt.printerjob=apple.awt.CPrinterJob juinox.launcher_1.1.0.v20100507.jar java.class.version=50.0 java.endorsed.dirs=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/endorsed java.ext.dirs=/Library/Java/Extensions:/System/Library/Java/Extensions:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/ext java.home=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home java.io.tmpdir=/var/folders/kW/kWTF5gdXGGCeNVVz5KZUV++++TI/-Tmp-/ java.library.path=.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java java.runtime.name=Java(TM) SE Runtime Environment java.runtime.version=1.6.0_24-b07-334-10M3326 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.6 java.vendor=Apple Inc. java.vendor.url=http://www.apple.com/ java.vendor.url.bug=http://bugreport.apple.com/ java.version=1.6.0_24 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Apple Inc. java.vm.version=19.1-b02-334 line.separator= Reproducible: Always Steps to Reproduce: 1. Create dependency from a workspace TS model project to an external module jar 2. import some artifacts to this Workspace TS model project's diagram 3. delete the dependency to the project 4. dangling artifacts are still shown in the diagram
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.
