Community
Participate
Working Groups
On eGit 0.10.1 (which is not available in the Bugzilla Versions BTW) I've noticed that Linked File Resources are not yet handled correctly? For example, on the MIFOS-4099__BetterWorkspace branch of my git@github.com:vorburger/mifos-head.git repo, in the mifos-parent folder/Eclipse project (https://github.com/vorburger/mifos-head/tree/MIFOS-4099__BetterWorkspace/mifos-parent), there are two linked file resources (pom.xml & pom.xml.readme.txt). -- BTW: What & how these are used for, if interested / relevant, is described in "Root directory (mifos-parent pom.xml) and Eclipse" on http://mifosforge.jira.com/wiki/display/~vorburger/WorkspaceSettings eGit always shows those two files as Status Unknown - seeming to think they are files physically in the mifos-parent folder (when they are not; they are just Eclipse-level 'links' to the files one level up in the directory hiearchy). Ideally, one would expect eGit to use the appropriate Eclipse workbench API and used the resolved location. Alternatively, a more minimal approach would be to have eGit ignore linked resources (for now).
*** Bug 346381 has been marked as a duplicate of this bug. ***
I made two patches that should resolve this issue by ignoring linked resources. These patches can be found attached to bug #347885 and bug #327407. They should also fix 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's a merging of the two patches mentioned above, plus some additions to cover a few more areas where linked resources should be ignored.
*** Bug 347885 has been marked as a duplicate of this bug. ***
Is there anything blocking inclusion of the above patch? I see no negative comment on last gerrit patch set.
merged as 199f7e89afbd2149c1809138204c7ac539a17b7e
*** Bug 371967 has been marked as a duplicate of this bug. ***