Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359819 - Pull command causes handler conflict
Summary: Pull command causes handler conflict
Status: VERIFIED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 1.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 361393 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-04 06:46 EDT by Dani Megert CLA
Modified: 2011-10-20 13:51 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2011-10-04 06:46:41 EDT 
1.2.0.201110021920

I get this each time I start Eclipse:

!ENTRY org.eclipse.ui.workbench 2 0 2011-10-04 12:42:51.660
!MESSAGE A handler conflict occurred.  This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2011-10-04 12:42:51.660
!MESSAGE Conflict for 'org.eclipse.egit.ui.team.Pull':
HandlerActivation(commandId=org.eclipse.egit.ui.team.Pull,
	handler=org.eclipse.egit.ui.internal.repository.tree.command.PullCommand,
	expression=org.eclipse.core.internal.expressions.IterateExpression@71c93206,sourcePriority=1073741824)
HandlerActivation(commandId=org.eclipse.egit.ui.team.Pull,
	handler=org.eclipse.egit.ui.internal.actions.PullFromUpstreamActionHandler,
	expression=org.eclipse.core.internal.expressions.IterateExpression@338cc288,sourcePriority=1073741824)
Comment 1 Remy Suen CLA 2011-10-10 08:41:10 EDT 
My fault. It was caused by the fix for bug 356781.

I've pushed a change set to Gerrit for review.
http://egit.eclipse.org/r/#change,4337
Comment 2 Matthias Sohn CLA 2011-10-10 18:21:40 EDT 
merged as 2d40e542dca869c8f36175001e0620c8629fe3dd
Comment 3 Dani Megert CLA 2011-10-20 09:04:22 EDT 
Verified in 1.2.0.201110190928.
Comment 4 Remy Suen CLA 2011-10-20 13:51:40 EDT 
*** Bug 361393 has been marked as a duplicate of this bug. ***