Community
Participate
Working Groups
Build Identifier: if one has a "bad" project in their workspace, you can get into an endless loop between getMapping() and getMappingForNonExistentResource(). This patch is a simple one-liner. There's another patch for ResourceUtil isNonWorkspace() as well, but I dunno if it's needed. Instead of getLocation() I did getLocationURI(), as that will resolve "virtual" stuff (like the ultimately "bad" RSE project I had perhaps)-- but as I said, I dunno if virtual stuff should be resolved. The null check is probably a must tho. Apologies for not going the gerrit route. Reproducible: Always Steps to Reproduce: 1.have a non-existent/error-ed project in your workspace 2.start eclipse 3.
Created attachment 208661 [details] patch for repository mapping null check now that I see it, I wonder if I should have done getLocationURI here too. Whateves.
Created attachment 208662 [details] resource util tweak not sure if this is needed, see ticket
Hi, Could you push this change to Gerrit for review? Instructions are here: http://wiki.eclipse.org/EGit/Contributor_Guide#Contributing_Patches
Looks like this has been fixed in e65101e7eeb28cd9cdb4bc1c7702fe91a59c534f or earlier