Dashboard > WOProject / WOLips > ... > Tutorials > java.lang.Object cannot be resolved
  WOProject / WOLips Log In View a printable version of the current page.  
  java.lang.Object cannot be resolved
Added by Kieran Kelleher, last edited by Kieran Kelleher on Jul 27, 2007  (view change)
Labels: 

Introduction

You may import a project from CVS, Subversion or somewhere and you have a lot of red x's, and you did not expect it. Usually this means you have build path problems. For example, a colleague recently followed the tutorial for importing Wonder source into Eclipse and after the Workspace was built he had many red x's. The following error gives a clue

Problem

The problem here is the build path setting. The cause can be as simple as the person who last edited the project has selected a different JVM path. So looking at the build path for the project in this case shows that the JVM cannot be found (which is why the most basic class, java.lang.Object, could not be found)

Solution

Selecting the unbound JVM library and clicking edit shows:

Selecting the default System JVM fixes the problem

Afterwards you may need to do a project (or workspace) clean and rebuild to get rid of all the red x's (aka. build errors)

Maybe we should rename this page and explain how to fix build path issues in general

Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.4 Build:#809 Jun 12, 2007) - Bug/feature request - Contact Administrators