| MacOS X build -- Cannot find the class file for java.lang.Object [message #385143] |
Mon, 11 May 2009 23:04 |
 Oisin Hurley
Messages: 204
Registered: July 2009 |
Senior Member |
|
|
This (or something like it) has come up before, I believe and there are
some relevant messages that have already been posted
http://dev.eclipse.org/newslists/news.eclipse.tools.buckmins ter/msg00776.html
http://dev.eclipse.org/newslists/news.eclipse.tools.buckmins ter/msg00794.html
This issue only occurs for me on my MacBook Pro when I am doing
a local, headless build. There's no problem building on the b.e.o.
infrastructure, which is a ppc linux box.
The symptom presents as:
[java] org.eclipse.core.runtime.CoreException: The project was not
built since its build path is incomplete. Cannot find the class file for
java.lang.Object. Fix the build path then try building this project
[java] at
org.eclipse.buckminster.core.internal.actor.AbstractBuildInt egrationActor.internalPerform(AbstractBuildIntegrationActor. java:53)
[java] at
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:201)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
[java] at
org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:198)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
[java] at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
[java] at
org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
[java] at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
[java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
[java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
When I open the headless build workspace in the IDE, I see an error marker
on a
file :
The type java.lang.Object cannot be resolved. It is indirectly referenced
from required .class files
If I clean the problem project in the IDE, and allow it to rebuild, the
error marker
goes away and I get a successful build.
Perhaps there is something the matter with the particular project that
causes
the issue - I'm not sure where I should look in Buckminster to see the
relevant
structures etc that are being passed to the Eclipse incremental builder...
--oh
You'll need to have a Mac to reproduce this, but a couple of hints of
where to look
|
|
|
Powered by
FUDForum. Page generated in 0.02955 seconds
] 
Search
Help
Register
Login
Home
