Moin Craig,
it's a bug in WOLips. The reason is a missconfigured launch
configuration. It happens when the launch configuration is created via
the context menu. The problem does not occur with a launch config
created within the "Run..." dialog.
A fix for it is in the cvs.
Ulrich
Am 16.12.2004 um 02:45 schrieb Craig Battis:
> We have 3 developers with exact same setup of Eclipse (3.0.0), WOLips
> (.82), Java (1.4.2), WO (5.2.3), etc. When we create an application
> with the component classes in packages, (/src/com/company/appl), 2 of
> us have problems with the error "Unable to find component class named
> XXX". One developer has no problems whatsoever. We are sharing the
> project in CVS, so all project files are the same. Comparing the
> debug/run launch properties also shows no differences.
>
> Searching this mailing list has shown several entries over the years
> with folks running into the same problem. Based on those entries, we
> got the 2 problem installations to work by adding to the classpath the
> source folder /build/project.woa/Contents/Resources/Java.
>
> My question is has anyone determined what causes these problems with
> classpath to occur? If one of our developers can run with just the
> default classpath, there must be a property or a setting or a file
> somewhere else that is causing differences in our classpaths. Since
> the project is in CVS, all project files are the same between us.
>
> Craig.
This archive was generated by hypermail 2.0.0 : Thu Dec 23 2004 - 15:32:45 EST