This seems to have fixed my problem - thanks!
Regards,
Jake MacMullin
Mike Schrag wrote:
> OK I went ahead and rolled back ... Incidentally, I saw an anomaly
> with classpath management as well where it appears that an old bug
> came bug -- the one where if you have the same named framework in /
> Library/Frameworks and /System/Library/Frameworks, both will be
> checked. So Garry -- if you could take another look at that patch
> and maybe redo it based off of the current HEAD version rather than
> the original version you patched from, that would be probably make
> for a smoother transition.
>
> On Sep 19, 2005, at 8:32 AM, Mike Schrag wrote:
>
>> So this didn't happen before the new classpath code? Garry -- any
>> ideas? I'm thinking we should roll back to the old version until
>> Garry gets a chance to look into this.
>>
>> On Sep 19, 2005, at 5:46 AM, Guido Neitzer wrote:
>>
>>
>>> On 19.09.2005, at 10:43 Uhr, Guido Neitzer wrote:
>>>
>>>
>>>
>>>> This doesn't fix anything here - it's just a different kind of
>>>> thing. Again: I'm not talking about frameworks. There I had the
>>>> same thing you have described a few days ago. But this is not my
>>>> current problem.
>>>>
>>>>
>>>
>>> So, just for the record ...
>>>
>>> I'm up and running again. Have recovered a WOLips v2.0.0.47 from my
>>> backup and installed this. So, my classpath issues are resolved and
>>> also Eclipse is working as expected.
>>>
>>> Lost 4 hours, but that's life.
>>>
>>> cug
>>>
>>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Mon Sep 19 2005 - 20:49:08 EDT