| Summary: | After installing m2eclipse i get error "A handler conflict occured" | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | andy <andy.engel> |
| Component: | m2e | Assignee: | Project Inbox <m2e.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | fjguodong, pascal |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
andy
I also tested with only installing m2eclipse. - and theres the error, too! Steps to Reproduce: 1. Download and start eclipse classic 3.5.2 2. install maven integration (0.12.0.20101115-1102.jar)for eclipse from updfate site http://m2eclipse.sonatype.org/sites/m2e 3. restart eclipse and look into error log Here the log file from now: !SESSION 2010-12-23 14:32:49.078 ----------------------------------------------- eclipse.buildId=M20100211-1343 java.version=1.6.0_23 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE Command-line arguments: -os win32 -ws win32 -arch x86 -data workspace !ENTRY org.eclipse.ui.workbench 2 0 2010-12-23 14:33:06.437 !MESSAGE A handler conflict occurred. This may disable some commands. !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2010-12-23 14:33:06.437 !MESSAGE Conflict for 'AUTOGEN:::org.maven.ide.eclipse.openPomDependencyNode/org.maven.ide.eclipse.ui.openPomDependency': HandlerActivation(commandId=AUTOGEN:::org.maven.ide.eclipse.openPomDependencyNode/org.maven.ide.eclipse.ui.openPomDependency, handler=ActionDelegateHandlerProxy(null,org.maven.ide.eclipse.actions.OpenPomAction), expression=WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@1f09a31),sourcePriority=16384) HandlerActivation(commandId=AUTOGEN:::org.maven.ide.eclipse.openPomDependencyNode/org.maven.ide.eclipse.ui.openPomDependency, handler=ActionDelegateHandlerProxy(null,org.maven.ide.eclipse.actions.OpenPomAction), expression=WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@1f09a31),sourcePriority=16384) !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2010-12-23 14:33:06.437 !MESSAGE Conflict for 'AUTOGEN:::org.maven.ide.eclipse.openProjectPageDependencyNode/org.maven.ide.eclipse.ui.openPomDependencyUrl': HandlerActivation(commandId=AUTOGEN:::org.maven.ide.eclipse.openProjectPageDependencyNode/org.maven.ide.eclipse.ui.openPomDependencyUrl, handler=ActionDelegateHandlerProxy(null,org.maven.ide.eclipse.actions.OpenUrlAction:org.maven.ide.eclipse.openProjectPage), expression=WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@1f09a31),sourcePriority=16384) HandlerActivation(commandId=AUTOGEN:::org.maven.ide.eclipse.openProjectPageDependencyNode/org.maven.ide.eclipse.ui.openPomDependencyUrl, handler=ActionDelegateHandlerProxy(null,org.maven.ide.eclipse.actions.OpenUrlAction:org.maven.ide.eclipse.openProjectPage), expression=WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@1f09a31),sourcePriority=16384) I hope someone can fix it. Because otherwise our company cannot programm with eclipse. Hey, now my entry is from last year and no one has answered to the bug request. Have anyone the possibility to fix the bug????? Otherwise the big company i work for have to change the development environment because we need this m2Eclipse Version to do our work. Please answer to this bug request. i hope i will get an information about the problem and how to fix it. It is really important to get an information for me. Thanks in advance. now i tried with the new version M2Eclipse 0.12.1, too. theres the same bug too. Please fix it. it is really important. we can not develop until the bug is fixed. anyone, plase answer. This has been fixed in 0.13 that is work in progress until mid June when Indigo ship. In the meantime you can try it from http://download.eclipse.org/technology/updates/M or http://download.eclipse.org/technology/updates/N if you want to be on the bleeding edge. After installing m2eclipse 0.12.0 on eclipse 3.5 I meet the same problem! I try to install old version m2e(0.10.2.20100623-1649), then the error log disapear no longer! Hope it can help you! |