combined EMF / GMF Editor throws conflicting handler message
I used this article
(http://www.eclipse.org/articles/article.php?file=Article-Integrating-EMF-GMF-Editors/index.html)
to combine my EMF and GMF Editor. This works fine so far with eclipse Juno
4.2.0. But after updating to 4.2.2 or Kepler, I get this messages when
switching between my EMF and GMF tabs:
!ENTRY org.eclipse.ui 4 4 2013-09-11 13:11:40.289
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.undo:
{ActionHandler(org.eclipse.gmf.runtime.common.ui.action.actions.global.GlobalUndoAction@ab287)}
vs {ActionHandler(org.eclipse.emf.edit.ui.action.UndoAction@4eeb3f)}
!ENTRY org.eclipse.ui 4 4 2013-09-11 13:11:40.293
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.paste:
{ActionHandler(org.eclipse.gmf.runtime.common.ui.action.internal.actions.global.GlobalPasteAction@b4519b)}
vs {ActionHandler(org.eclipse.emf.edit.ui.action.PasteAction@59abfd)}
!ENTRY org.eclipse.ui 4 4 2013-09-11 13:11:40.296
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.redo:
{ActionHandler(org.eclipse.emf.edit.ui.action.RedoAction@1f44cbf)} vs
{ActionHandler(org.eclipse.gmf.runtime.common.ui.action.actions.global.GlobalRedoAction@1dac3e4)}
!ENTRY org.eclipse.ui 4 4 2013-09-11 13:11:40.299
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.delete:
{ActionHandler(org.eclipse.emf.edit.ui.action.DeleteAction@1227e51)} vs
{ActionHandler(org.eclipse.gmf.runtime.common.ui.action.internal.actions.global.GlobalDeleteAction@1932bb6)}
!ENTRY org.eclipse.ui 4 4 2013-09-11 13:11:40.302
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.cut:
{ActionHandler(org.eclipse.emf.edit.ui.action.CutAction@c4eb64)} vs
{ActionHandler(org.eclipse.gmf.runtime.common.ui.action.internal.actions.global.GlobalCutAction@3a26f2)}
!ENTRY org.eclipse.ui 4 4 2013-09-11 13:11:40.305
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.copy:
{ActionHandler(org.eclipse.emf.edit.ui.action.CopyAction@81c5c9)} vs
{ActionHandler(org.eclipse.gmf.runtime.common.ui.action.internal.actions.global.GlobalCopyAction@1e043b2)
This is really anoying since I searched already a few hours to find a
solution. What I don't understand is that this messages don't occur with
eclipse Juno 4.2.0. Is there a way to tell eclipse which ActionHandler
should be used?
Cheers, Phil
No comments:
Post a Comment