Classpath not working

Question

My project requires the gif4j suite. So I set the classpath to "C:...\gif4j_pro_trial_2.3.jar" in the Environmental Variables window from my Control Panel. I know that when we have multiple values for classpath, you seperate them with a semi-colon. I did that too. But I'm still getting this error when I run the file.

Exception in thread "AWT-EventQueue-0" java.lang.Error: Unresolved compilation problems:
    The import com.gif4j.TextPainter cannot be resolved
    The import com.gif4j.Watermark cannot be resolved

I don't really understand what's going on here since I'm not the one who wrote the code. What am I missing?

have u tried compiling ur code again after setting the class path? — Ashwini Raman
– Ashwini Raman, Commented Mar 15, 2012 at 11:42

Matt McHenry · Accepted Answer · 2012-03-15 11:43:45Z

1

This error doesn't say anything about not being able to find the gif4j classes at runtime. Instead, it's saying that, when the code was compiled, those classes weren't available. javac does not produce these kinds of errors (instead it simply fails to compile), so I'm assuming this code was compiled by Eclipse. In that case, you should check your Eclipse project configuration and make sure that the gif4j libraries are properly included there.

answered Mar 15, 2012 at 11:43

Matt McHenry

21.2k8 gold badges68 silver badges66 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Uday Kanth Over a year ago

Ok I do believe the project was compiled in Eclipse. But I'm new to it so I don't know where to check. So, anyway, what you're saying is that I should properly include the libraries and compile the code again? No need to bother about about setting the classpath variable?

Matt McHenry Over a year ago

Yes, you should properly include the libraries and compile the code again. You probably will also need to set the classpath variable to run the code, but you won't know that for sure until you've got the code compiled correctly.

Andreas Dolk · Accepted Answer · 2012-03-15 16:43:49Z

1

The throw new Error(..() statement has been created by eclipse. Whenever eclipse can't compile a class because of compile time errors in methods, it tries to create stubs for those methods. So you'll always find a class file, even if the source code has errors.

Such a method would look like (example):

public long calculate(long a, long b) {
   throw new Error("Unresolved compilation problems");  // + additional information
}

It doesn't actually exist in your source, it's only created on byte code level.

So, what has happened: Most likely that you (or someone else) ignored error markers in your project and now tried to use the class files in the bin folder. You can't fix that problem at runtime, you have fix the project to create properly compiled classes.

edited Mar 15, 2012 at 16:43

answered Mar 15, 2012 at 13:37

Andreas Dolk

115k20 gold badges185 silver badges275 bronze badges

Collectives™ on Stack Overflow

Classpath not working

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related