Community
Participate
Working Groups
I often do some work in other tools, including creating an ANT build script, lib dir, src dir, and build dir, before firing up Eclipse. (I expect this to happen less often as launch times and editor responsiveness improve in the still young SWT implementation for MacOS X.) When I attempt to create a new project in one of these existing directories, it will fail in 3.0M2 and in the Aug. 3 release of Eclipse. To reproduce: Create a new directory in the file system. Give that directory a src dir with an appropriately packaged java file, a lib dir with some libs, and a build dir. Launch Eclipse 3.0M2 Attempt to create a new Java project with any name, though this example used "Spheres" as the project name, and with a home of the new directory you just created. The message on the screen is "Spheres does not exist" The log contains: !MESSAGE Internal Error !STACK 1 Java Model Exception: Java Model Status [Spheres does not exist.] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:437) at org.eclipse.jdt.internal.core.JavaModelManager.getPerProjectInfoCheckExistence(JavaModelManage r.java:848) at org.eclipse.jdt.internal.core.JavaProject.getPerProjectInfo(JavaProject.java:1544) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1635) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1621) at org.eclipse.jdt.internal.core.JavaProject.buildStructure(JavaProject.java:217) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:198) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:448) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:269) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:255) at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1282) at org.eclipse.jdt.internal.core.JavaProject.getNameLookup(JavaProject.java:1290) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1004) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:988) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:981) at org.eclipse.jdt.internal.ui.wizards.ClassPathDetector.visitCompilationUnit(ClassPathDetector.java:2 16) at org.eclipse.jdt.internal.ui.wizards.ClassPathDetector.visit(ClassPathDetector.java:273) at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:50) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:76) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80) at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:119) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:60) at org.eclipse.jdt.internal.ui.wizards.ClassPathDetector.<init>(ClassPathDetector.java:62) at org.eclipse.jdt.internal.ui.wizards.NewProjectCreationWizardPage.updateProject(NewProjectCreatio nWizardPage.java:124) at org.eclipse.jdt.internal.ui.wizards.NewProjectCreationWizardPage$1.run(NewProjectCreationWizard Page.java:86) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758) at org.eclipse.jdt.internal.ui.wizards.NewProjectCreationWizardPage.changeToNewProject(NewProject CreationWizardPage.java:94) at org.eclipse.jdt.internal.ui.wizards.NewProjectCreationWizardPage.setVisible(NewProjectCreationWiz ardPage.java:64) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:959) at org.eclipse.jface.wizard.WizardDialog.access$1(WizardDialog.java:940) at org.eclipse.jface.wizard.WizardDialog$3.run(WizardDialog.java:929) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:84) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:927) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:684) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316) at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1016) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2180) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1878) at org.eclipse.jface.window.Window.runEventLoop(Window.java:583) at org.eclipse.jface.window.Window.open(Window.java:563) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:107) at org.eclipse.jface.action.Action.runWithEvent(Action.java:842) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java :542) at org.eclipse.jface.action.ActionContributionItem.access$4(ActionContributionItem.java:496) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:468) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1016) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2180) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1878) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1680) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1663) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.core.launcher.Main.basicRun(Main.java:291) at org.eclipse.core.launcher.Main.run(Main.java:747) at org.eclipse.core.launcher.Main.main(Main.java:583) !ENTRY org.eclipse.jdt.core 4 969 Aug 22, 2003 13:07:30.330 !MESSAGE Spheres does not exist. I will try again with M3 in a week. Note - this works with M1, and thus I usually launch M1, create my project, quit, and then create the project again in M2. It picks up the entries in the .classpath file happily, and does not fail.
Your scenario is different from bug #41583 but the culprit is the same. *** This bug has been marked as a duplicate of 41583 ***
*** Bug 41996 has been marked as a duplicate of this bug. ***