Bug 1480900 – Opening git project from a `git worktree` directory fails

Bug 1480900 - Opening git project from a `git worktree` directory fails

Summary:	Opening git project from a `git worktree` directory fails

Status:	NEW

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	eclipse-jgit (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Mat Booth
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-08-12 14:33 EDT by Christopher Tubbs
Modified:	2017-08-14 05:40 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Eclipse Project	477475	None	None	None	2017-08-12 14:33 EDT

Groups: None (edit)

Description Christopher Tubbs 2017-08-12 14:33:02 EDT

Description of problem:
I attempted to import an existing Maven project into Eclipse from a `git worktree` location, and got an error with the git Auto-share feature.

Version-Release number of selected component (if applicable):
eclipse-jgit-4.8.0-2.fc26.noarch

How reproducible:
Always

Steps to Reproduce:
1. git clone some-project && cd some-project
2. git worktree add ../tmp some-branch
3. Open Eclipse and import existing project form ../tmp

Actual results:
Error message about failing to Auto-share git project

Expected results:
Git feature active in Eclispe, tracking git changes

Additional info:
This appears to be a known upstream bug with eclipse-jgit https://bugs.eclipse.org/bugs/show_bug.cgi?id=477475

Note You need to log in before you can comment on or make changes to this bug.