| Summary: | Committing a linked source fails | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Gorkem Ercan <gorkem.ercan> | ||||
| Component: | Core | Assignee: | Project Inbox <egit.core-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipse.org, robin.rosenberg | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 2.3 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Gorkem Ercan
A linked resource is basically a 'virtual' resource, its location in the Eclipse project does not correspond to the same location in the filesystem, but to somewhere else. That would explain the FileNotFoundException: there's not way it can be committed to git since it's not there in the filesystem. This bug shows a lack of support for Linked Resources. EGit should show a proper warning instead of failing like that. See Bug #333338. Created attachment 197370 [details] Fix - gerrit change supersedes this patch Simple patch that ensure linked resources are ignored in key points of egit core and ui logic. I made this patch while resolving bug #347885, so another patch is attached there. These two patches should probably resolve a few bugs related to linked resources such as bug #333338 and bug #347454. They also solve the apparently unreported case where the EGit project sharing dialog lists repositories totally unrelated to the selected project when it contains linked folders pointing to files below another git repository. Note that Eclipse docs state it is recommended for a Team Provider to ignore linked resources, see section titled "Strategies for Handling Linked Resources" there: http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/team_resources.htm I've submitted the following change request for this bug: http://egit.eclipse.org/r/3680 It fixes this bug, plus cover a few more areas where linked resources should be ignored. This bug should be marked as a duplicate of the more generic bug #333338 where the change request is referenced. Merged in 2.3.0 |