Community
Participate
Working Groups
I noticed today (while creating a "fresh workspace", from scratch) that with EGit's ability to "search for nested projects" during "import into workspace" that there a large number that show up with a name of "org.eclipse.jst.core" ... naturally, only one of them it the "correct" one to import as a top level project into IDE's workspace. The other (16 or so) come from the "workspace" projects in org.eclipse.jdt.core.tests.model There are 33 projects in there, all together, these 16 or so have <name>org.eclipse.jdt.core</name> in their .project file. A quick peek at the others appears they have "directory name" as there project name, such as org.eclipse.jdt.core.tests.model/workspace/AccessRestrictions has in its .project file <name>AccessRestrictions</name> It'd be easier to pick the "right" jdt.core bundle to import into workspace if the other test projects were similarly named with their "folder name". Initially, since my window was not very wide, and I was hasty, I imported everything that started with "org.eclipse.jdt" ... but naturally, during import, "only one can win" when there projects with same name, so it took me a while to figure out what was wrong with "jdt.core". (And, nothing really wrong with it ... just wrong one).
(In reply to David Williams from comment #0) > ... there a large number that show up with a name of > "org.eclipse.jst.core" ... naturally, only one of them it the "correct" one > to import as a top level project into IDE's workspace. Its probably obvious, but of course I meant "org.eclipse.jdt.core"
