|
|
|
| Re: Testing - please ignore [message #105372 is a reply to message #105179] |
Tue, 27 September 2005 15:55  |
Eclipse User |
|
|
|
Peter Toye wrote:
> ...then can you answer my next question (the one posted 30 minutes later)?
>
> Peter
The SWT question? Don't know that I can help much. I've avoided getting
into SWT myself. :-) But as I see from the message, that's not really
the issue (other than the specifics of "the cheat sheet" you mention,
which seems to be an SWT project "feature" of some sort).
Yes, it looks to me like a CLASSPATH type of problem, something I've
always hated about Java. Seems like a simple idea... tell the system all
the places where you can find the stuff you're depending on/using... but
it seems to be the source of many problems.
The "org/eclipse/swt..." stuff makes me assume in your HelloWorld.java
file you do an "import org.eclipse.swt..." and it can not find that
directory structure on your classpath, nor can it find that directory
structure "simulated" in a .jar/.zip file (which it also expects to find
somewhere in your classpath), or ... well, I don't know all the
different ways Java tries to make it possible to find what you need. The
fact that it is reported as a directory structure when most people would
actually see it "embodied" in a org.eclipse.swt...jar file is part of my
whole complaint here against Java!
Do a "set" command and see if the classpath variable is set, and what it
is set to. Go into Eclipse and see what your properties say are the
places *it* is looking to find stuff. Adjust appropriately! (I'm being
vague here... as I said, I know nothing about "the cheat sheet"... I
don't know if you're on Windows or Linux [thus I chose "set" as the
universal "look at variables" suggestion], I'm not even sure how
comfortable you are on said OS's command line... give me a little more
to go on here if this doesn't help and I'll try more.)
--
RDS
|
|
|
Powered by
FUDForum. Page generated in 0.08691 seconds
Home