Community
Participate
Working Groups
Created attachment 200732 [details] wrong error message I have added a maven module to an existing git repo in a sub-folder. All other projects in the same git repo are already imported and shared via EGit. I import the new maven project and try to use Team > Share. After selecting the repository in the parent folder, I get the wrong error message " Can not move project nexus-staging-plugin to target location C:\git\sap_git\releasetools\nexus-staging-plugin, as this location overlaps with location C:\git\sap_git\releasetools, which contains a .project file" There is nothing to move here, the project stays where it is since source and target folder are the same (see screenshot). I would have expected the UI to simply ask me if I would like to use the existing git repository in the parent folder? yes -> Finish. This was much easier in previous EGit versions. After some trying around I found that if I check "Use or Create Repository in Parent Folder of Project", the import works. It seems like the straightforward scenario of sharing a project in a subfolder of an existing git repo has been rendered almost unusable. Why am I confronted with the complexity of moving projects if I didn't explicitly ask for it? Other usability issues in this wizard: - checkbox "Use or Create Repository..." displays a four-line tooltip (see screenshot) telling me "... this is not recommended for several reasons mentioned in the EGit user guide" -- what's the point? Nobody will read a four-line tooltip. - when I click checkbox "Use or Create Repository...", the complete wizard page is exchanged on the fly. If there is a choice to make (either move project or reuse existing git repository), there should be radio buttons on the first page, I make my choice and press Next to get to the specific wizard page (if necessary). This would move all the complicated move UI out of the initial wizard page which makes it confusing.
Created attachment 200734 [details] four-line confusing tooltip
(In reply to comment #0) > It seems like the straightforward scenario of sharing a project in a subfolder > of an existing git repo has been rendered almost unusable. Why am I confronted > with the complexity of moving projects if I didn't explicitly ask for it? I am sharing the frustration of Jan. I can understand that EGit has some legacy UIs that need to be reworked - and that takes time. But this is a new "feature"!! And still the UI could barely be worse...
