I forwarded it to Uli. I don't know enough of the startup stuff to
mess with it...
Cheers, Anjo
Am 22.05.2006 um 17:38 schrieb Watkins, Garry:
> Anjo, the patch that I submitted to you a few weeks ago fixes that
> problem
> of duplicate frameworks.
>
> Thanks
> Garry
>
>
> On 5/22/06 10:58 AM, "Anjo Krank" <kran..ogicunited.com> wrote:
>
>> The short story is that WOLips uses a path to discover frameworks,
>> regardless of the setting. User > Roots > /Library/ > /System/
>> Library.
>>
>> This was pretty ill-conceived by me and should really go away and one
>> of these days it probably will, but for now you can just delete the
>> frameworks in ~/Roots or rename your ~/Roots to sth else and set the
>> build.root variable when calling ant.
>>
>> Cheers, Anjo
>>
>> Am 22.05.2006 um 16:49 schrieb John Huss:
>>
>>> I always seem to have problems with the "WebObjects Frameworks"
>>> Library, so I end up not using it.
>>>
>>> When initially adding the library to my project, it places
>>> "/Users/John/Roots/JavaWOExtensions.framework" on my path 3 times
>>> (by
>>> default it is checked in each of the different locations.
>>>
>>> If I check Local->ERExtensions and Finish, it adds the framework
>>> from
>>> /Users/John/Roots instead of /Library/Frameworks. And if I edit the
>>> library again, I find that ExternalBuildRoot->ERExtensions is now
>>> also
>>> checked and if I press Finish, I end up with duplicate entries for
>>> ERExtensions, with both pathed to /Users/John/Roots.
>>>
>>> What's going on?
>>>
>>> John
>>
>
> --
> Garry Watkins
>
> Database Administrator
> Motley Rice LLC
> 843-216-9639
>
>
>
>
>
>
> Confidential & Privileged
>
> Unless otherwise indicated or obvious from its nature, the
> information contained in this communication is attorney-client
> privileged and confidential information/work product. This
> communication is intended for the use of the individual or entity
> named above. If the reader of this communication is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error or
> are not sure whether it is privileged, please immediately notify us
> by return e-mail and destroy any copies--electronic, paper or
> otherwise--which you may have of this communication.
>
>
>
This archive was generated by hypermail 2.0.0 : Mon May 22 2006 - 11:42:28 EDT