OK, I just went into WebObjects Frameworks -> Configure and unchecked
*all* the localroot frameworks (since I have them linked in Build
Path already) and still no success. BTW, the classpath file did not
change after doing this. OK, here is some screenshots of everything
relevant after removing the frameworks from WO frameworks confgure
dialog ..... anyone got any idea before I revert back to my last
version of wolips (well for today anyway)...
On Nov 19, 2007, at 8:52 AM, Ulrich Köster wrote:
> Moin,
>
> sorry, currently I have a really large mail back log.
>
> Either add the framework or the project to the classpath. By the
> way it's only a problem with WOnder projects..............
>
> Uli
> Am 19.11.2007 um 14:45 schrieb Mike Schrag:
>
>>> OK, just upgraded to latest WOLips .... now getting the
>>> following..... What is the "new" way to have a framework added to
>>> the project so that I am using the workspace version and so that
>>> the /Library/Frameworks version is used in deployment later?
>> There is no new way right now -- It's a bug in the new classpath
>> stuff, but I'm not sure what actually changed between the two, so
>> I'm not exactly sure how to fix it ... I happen to have already
>> had a hacked NSBundle, so mine prevents this exception --
>> admittedly a pretty lame fix. I think Ulrich has been busy with
>> other things recently.
>>
>> ms
>>
>
This archive was generated by hypermail 2.0.0 : Mon Nov 19 2007 - 09:23:29 EST