Hi Collin,
Collin VanDyck schrieb:
> Franz,
>
[quoted text clipped - 4 lines]
> (Add Jars...) as well as any jars that might be referenced once your
> project is deployed (Add external Jars...)
for a while it fixed the problem - but probably it was just an accident ;-)
> Also, if you are having general package recommendation errors with
> Eclipse, make sure that your source folders are set correctly.
I don't get it. What does the source folders mean? (window-pref
java>build path)
I have my java classes and my eclipse-project files in eclipse/workspace/
In "Source folder name" is the value src
In "output folder name" is the value bin
> As an example, in my Java project, I have a src/java directory that
> contains all of my java source. Under project properties -> Java Build
> Path -> Source (tab), I added the folder src/java. That resolves a lot
> of package related errors that Eclipse will report when it thinks that
> your project root is the base for your Java source files.
I added under project-properties java build path>Source edit included.
There added the folder with all my source (wgims). But it refreshed only
and after a short while the errors occured again.
One (maybe) interesting error I forgot to note:
In some classes eclipse say (the error has no location line):
A class file was not written. The project may be inconsistent, if so try
refreshing this project and building it
Thanks in advance.
greez Franz