GMF Troubleshooting 9

GMF

1. GMF Troubleshooting
2. GMF Troubleshooting 2
3. GMF Troubleshooting 3
4. GMF Troubleshooting 4
5. GMF Troubleshooting 5
6. GMF Troubleshooting 6
7. GMF Troubleshooting 7
8. GMF Troubleshooting 8
9. GMF Troubleshooting 9

Conflict for xxx.LoadResourceAction':HandlerActivation(commandId=xxx.LoadResourceAction, handler=xxx.part.LoadResourceAction, expression=,sourcePriority=0) HandlerActivation(commandId=xxx.LoadResourceAction, handler=xxx.part.LoadResourceAction, expression=,sourcePriority=0)

This can occur if, in your generated plugin.xml, there are multiple org.eclipse.ui.commands extensions with the same ID.

In my case this occured because my .gmfgen had two Gen Editor Generator > Context Menu items. Perhaps this is from a previous migration. Removing them ensured the error would not happen again.

I wrote this test case to check against existing gmfgen's to ensure this problem did not regress.

---

Error initializing element type "org.eclipse.gmf.tests.runtime.emf.type.core.employee": element type with same ID already exists.

These errors can be ignored. These errors come from the org.eclipse.gmf.tests.runtime.emf.type.core JUnit test plug-in, which can be removed from your launch configuration.