Bug 347571

Description Robin Rosenberg 2011-05-29 05:25:30 EDT

This could also be JGit, if EGit is acgually doing the right thing, which
I believe it is not. It cannot just checkout the index, since the index itlse
must also be reset with the "hard" option.

Add a new resource
Add it to the git repo
Remove the added resource from the file system (outside of eclipse)
Use Team>Reset with the Hard option
Expect: the new resource to be gone, both from workspace and index
Actuallly. The new resource is still in the index, though not visible in the  workspace.

More bugs:
If you attempt a commit the added index entry will show up in the commit dialog,
but committing it will fail with:

org.eclipse.jgit.api.errors.JGitInternalException: No changes
at org.eclipse.jgit.api.CommitCommand.createTemporaryIndex(CommitCommand.java:406)
at org.eclipse.jgit.api.CommitCommand.call(CommitCommand.java:192)
at org.eclipse.egit.core.op.CommitOperation.commit(CommitOperation.java:243)
at org.eclipse.egit.core.op.CommitOperation.access$6(CommitOperation.java:222)
at org.eclipse.egit.core.op.CommitOperation$1.run(CommitOperation.java:186)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957)
at org.eclipse.egit.core.op.CommitOperation.execute(CommitOperation.java:196)
at org.eclipse.egit.ui.internal.commit.CommitUI$2.run(CommitUI.java:252)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

The error message is quite confusing as the dialog onlt presents the "No changes" in the detail pane.