Community
Participate
Working Groups
[Component Diagram] Error messages at initialization it seems that there is a gmf error. What steps will reproduce the problem? 1. Create a papyrus model using papyrus perspective 2. Save and quit Eclipse 3. Restart Eclipse and open your model in Papyrus perspective You get errors in the error log. This doesn't prevent Papyrus from working but it is not a sane behavior. I experemimented also bugs when trying to work in a component diagram. -- Error Details -- Date: Wed Aug 03 18:24:49 CEST 2011 Message: Error initializing element type "org.eclipse.papyrus.diagram.component.Dependency_4010": element type with same ID already exists. It will be ignored. Severity: Error Product: Eclipse 1.4.0.20110609-1120 (org.eclipse.epp.package.modeling.product) Plugin: org.eclipse.gmf.runtime.emf.type.core Session Data: eclipse.buildId=I20110613-1736 java.version=1.6.0_24 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR Framework arguments: -product org.eclipse.epp.package.modeling.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.modeling.product
Created attachment 200833 [details] PbInitializationComponentDiagarmScreenView Initialialization pbs of the component diagram (gmf related problem). Remark In this example, I did not create a component diagram.
Created attachment 200836 [details] Log File of pb Model as been closed and reopened
after a regeneration of the component diagram, the errors/warnings messages was disappeared.
Does not appear to be fixed (tested on 0.8.1 nightly build 201108122014). The plugin.xml file does not seem to be correct on 0.8.X branch: - some svn merge conflict exists <!-- optionally, specify keybindings --> >>>>>>> .r4908 </plugin> - still duplicated extensions (related to the merge conflicts problem) - the following warning is not fixed : Conflict for 'org.eclipse.papyrus.diagram.component.LoadResourceAction' - the following warning is not fixed : Conflict for 'org.eclipse.papyrus.diagram.component.updateDiagram' Maybe your fix concerned the trunk, in that case is should also be applied to the 0.8.X branch.
Actually, the changes I made were on the trunk. I updated the 0.8.x branch, the problems have disappeared.