| Summary: | git not importable as Project after checkout | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Samuel Suther <s.suther> |
| Component: | Core | Assignee: | Jens Baumgart <jens.baumgart> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | caniszczyk, chuck, jkb, kbduzsrf, matthew, pohl.longsine, robin, stefan.lay |
| Version: | 0.8.1 | ||
| Target Milestone: | 0.9.0-M2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Samuel Suther
Fixed with 247ef7cd289b745715a7294517a558fdc70008c2. Thanks Jens. Is this resolved fixed for Mac OS X as well? Because with my EGit 0.9.1 and Eclipse 3.6.1 combo on OS X, the option to "Import as General Project" after clone/checkout leads to the same error message: "<project> overlaps another project", and while the future project name in that dialog is editable the directory path that should reflect the future name in its path end is grayed out and doesn't update when I change the name. Please try with 'EGit 0.10.1' which is the latest released version. If you hit the issue, report the bug. Oh, I'm sorry, the update feature didn't show me there's a new EGit version out. I tried it now with 0.10.1 and the result is the same: Importing as General Project after cloning is only possible if the clone didn't happen into the active workspace because the "Directory" text field that is grayed out doesn't reflect the value entered in "Project name" as its last path component. The problem is still there with Egit 0.11.3 in Eclipse 3.6.2. I just encountered this with EGit 0.12.1 on Eclipse Helios Service Release 2. (MacOS X 10.6.7). I see that this issue is marked as "RESOLVED FIXED". Is there another issue tracking this problem now? Indeed this isn't yet fixed, I've come across the same bug. Eclipse 4.2.0 EGit 2.0.0.201206130900-r, OS X 10.7.4. This bug is still in Eclipse 3.7.2 with egit 2.1.0.201209190230-r and Eclipse 4.2.1 with the same version of egit. I and about 30 co-workers are now migrating most of our Git projects to Netbeans until Eclipse figures out how to do an import correctly. Are you sure you also hit the bug using "Import as general project"? That case works here. If not, please file a new bug with the exact steps to reproduce and add a comment here linking to it. What did not work was using "Import existing projects" from the Git import wizard, in the case when the repository contains a .project, but with a different name than the directory on the file system. Please see bug 327975 for that, which has a proposed fix. |