Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350804

Summary:	Synchronize against an SVN bridge ref does nothing
Product:	[Technology] EGit	Reporter:	Missing name <avantnoisebot>
Component:	Core	Assignee:	Project Inbox <egit.core-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	arkinis
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Missing name

2011-06-30 07:50:39 EDT

Build Identifier: 20110615-0604

An ordinary Git reference that happens to be created by a git svn operation cannot be used in Team -> Synchronize.  The ref is listed in the Synchronize dialog but selecting it does nothing.  Similarly, it can be picked as the destination in the Custom sub-dialog, but in this case Finish does nothing.

Note that although the reference was created by a git svn operation, which is not supported in jgit/egit, the reference itself is an  ordinary git ref just like any other.  Nothing about is in any way specific to svn.


Reproducible: Always

Steps to Reproduce:
1.Import an SVN bridge repository with standard layout into Eclipse.
2.Edit and save any file in the master branch.
3.From the right-click menu on the project root, select Team -> Synchronize.
4. Note that refs/remotes/trunk appears in the submenu.  Select it.
5. Expected: Synchronization between master and refs/remotes/trunk; Found: nothing happens.
6: Repeat (3) but this time select "Custom..." from the submenu
7. Choose refs/remotes/trunk from the Destination pulldown
8. Click Finish
9. Expected: Synchronization between master and refs/remotes/trunk; Found: nothing happens.

Comment 1 Missing name

2011-06-30 08:21:06 EDT

One additional step: 
Disable the egit preference "Always launch fetch before synchronization", as this is not expected to work in this scenario

Comment 2 Eric Le Blouc'h

2011-11-09 10:44:37 EST

I have the same issue on version 1.1.0.201109151100-r on ubuntu.

In the eclipse log, I have the followink stack trace :

!ENTRY org.eclipse.ui 4 0 2011-11-09 13:31:21.840
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1937)
	at org.eclipse.egit.core.synchronize.dto.GitSynchronizeData.extractRemoteName(GitSynchronizeData.java:268)
	at org.eclipse.egit.core.synchronize.dto.GitSynchronizeData.<init>(GitSynchronizeData.java:111)
	at org.eclipse.egit.ui.internal.synchronize.GitSynchronizeWizard.performFinish(GitSynchronizeWizard.java:69)
	at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
	at org.eclipse.jface.window.Window.open(Window.java:801)
	at org.eclipse.team.internal.ui.synchronize.actions.SynchronizePageDropDownAction$1.run(SynchronizePageDropDownAction.java:40)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

Comment 3 Dariusz Luksza

2011-11-18 18:34:03 EST

Duplicate 363173

*** This bug has been marked as a duplicate of bug 363173 ***