> Hmmm I suppose yes that would make sense.
Actually it does not. During a normal launch, you don't get the
dependencies of the frameworks either and it can seriously muck with
your classpath (one could argue that you should, but this would
require a wholly new launching system, also for the shell launches).
I tried a few times to get rid of this, however this class path code
isn't really for the faint-hearted....
Cheers, Anjo
Am 26.02.2008 um 09:37 schrieb Andrew Lindesay:
> Moin Moin Uli;
>
> You mean it has to be removed from the build path of frameworks
> inside the workspace which the application project is using? Hmmm I
> suppose yes that would make sense. Thanks for that.
>
> cheers.
>
>> you have to remove the container from all dependencies in the
>> workspace also.
> ...
>>> I'm using "jar frameworks" on a project at the present time and so
>>> I removed the "WebObjects Frameworks" entry in the project build
>>> path in Eclipse. Now it still seems to try and load the "bundle
>>> frameworks" as well as the "jar frameworks". I know this was
>>> working before I updated wolips recently. I'm a bit confused as
>>> to how this is possible -- or should I file a bug?
>
> ___
> Andrew Lindesay
> technology : www.lindesay.co.nz
> business : www.silvereye.co.nz
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Feb 26 2008 - 03:42:41 EST