Dear Jeremy,
being different is acceptable if it works. Using the ~/.eclipse/
folder is the unixy way and is much better than having the ~/Developer/
Apps/eclipse folder writable by the whole world, or by many users. The
latter means that the Eclipse + WOLips system is broken. It's not
supposed to work that way...
I hope I am not the only one who thinks this is a serious issue. I
have filed a bug report, but am not sure if in the correct place.
Should I redo it as a WOLips bug rather than the binary installer bug?
http://issues.objectstyle.org/jira/browse/WOL-1025
Thanks
Rudy
On Jun 19, 2009, at 8:04 AM, Jeremy Matthews wrote:
> Yep...total bummer.
> Eclipse is _different_
>
> -j
>
> On Jun 18, 2009, at 7:49 PM, Rudolf B. Blažek wrote:
>
>> On Jun 19, 2009, at 7:31 AM, Q wrote:
>>
>>>> Here's the thing....the all-in-one installer changes ownership on
>>>> the Eclipse.app to root:admin, since most apps in /Developer/Apps
>>>> have ownership set this way.
>>>> Since /Developer is created when the WO frameworks are installed,
>>>> it seems like a natural fit.
>>>
>>> Unlike "proper" mac apps which use ~/Library/* for runtime config,
>>> eclipse directly modifies files and folders located within the
>>> 'eclipse' folder itself and therefore should have suitable
>>> ownership and/or permissions to be writeable by the user or it
>>> will not function correctly.
>>
>> The problem is that this is not the entire story. Eclipse uses the
>> folder ~/.eclipse/ for user-based config. But only if the main
>> eclipse folder is not writeable by the user that runs Eclipse.
>>
>> This works OK with Eclipse 3.4.1 + WOLips and with Eclipse 3.4.2
>> without WOLips
>>
>> It's only Eclipse 3.4.2 + WOLips that has problems.
>>
>> I believe this is a bug.
>>
>> Rudy
>
This archive was generated by hypermail 2.0.0 : Thu Jun 18 2009 - 21:40:49 EDT