tags:

views:

111

answers:

2

I've created a Java project from existing source with an Ant build script in Eclipse. I cannot run my project because Eclipse tells me that there is at least one error in it.

Now, I know that the project runs fine on the command line, so I suspect an Eclipse configuration error.

As far as I can tell, the only feedback that I have from Eclipse is

  1. a little red X on my project in the Package Explorer window Eclipse Error Package Explorer

  2. and dialog window when I try to run the project says there are errors in the project Eclipse Error Dialog

This is all wonderful, but what is the error?

Is there a "show me the next error" button somewhere?

In the past, on other Eclipse projects, I've notice other little red X's on folders containing source files with errors, the little red X's appear on the source files as well. I scanned (manually) through all of the source files and I haven't found any other red X's (again, where is the "next error" button?).

If I select the "Proceed" button I am greeted with a java.lang.NoClassDefFoundError for my main class, which makes me suspect a classpath issue. I've checked the classpath, and I'm fairly certain that it's correct. Is there a way to see the exact jvm command line that Eclipse is invoking? I realize that it might be invoking the JVM programmatically, and not on a "real" command line. In any case, is there a way, other than the run configuration dialog, to see what is actually happening when I hit the "Proceed" button?

+7  A: 

The errors are shown in the Problems view. If it is not opened, go to:

Window > Show View > Problems

alt text

Also accessible with the keyboard shortcut Alt+Shift+Q,X

Bozho
+3  A: 

Selecing Window -> Show View -> Problems will open the Problems view, that should have a list of all problems, their location and nature (it can be configured to show only project- or file-local problems, so you may also have to click on the project). Most likely you have a config error in your project, e.g. a reference to a JAR library that cannot be found.

Michael Borgwardt