Re: All-In-One Installer bug

From: Jeremy Matthews (jeremymatthew..ac.com)
Date: Fri Jun 19 2009 - 08:19:22 EDT

  • Next message: Ricardo J. Parada: "Re: All-In-One Installer bug"

    soooo....what should we do here (at least for the binary instaler)?
    Anyone?
    Bueller?

    We'd like to be careful about giving too many options, or doing to
    much on a per-user basis...I suppose we could add a simple app/script
    to change permissions, but it seems like more of an eclipse
    thing...not sure if its wise to fight it.

    -j

    On Jun 19, 2009, at 8:12 AM, Mike Schrag wrote:

    > 3.5 won't load them either, but with ZERO debug information. It
    > shows that it knows they're there, but they just aren't activated.
    > WTF.
    >
    > On Jun 19, 2009, at 7:52 AM, Mike Schrag wrote:
    >
    >> verified btw ... no idea why it's failing now. yay for osgi.
    >>
    >> On Jun 19, 2009, at 7:15 AM, Rudolf B. Blažek wrote:
    >>
    >>> Dear Q, forgive me, if my reply is too long:
    >>>
    >>>
    >>> Here is what fails:
    >>>
    >>> 1) Install Eclipse 3.4.2 into e.g. /Developer/Applications/eclipse
    >>> 2) Change the ownership of the install folder to root:admin
    >>> chown -R root:admin /Developer/Applications/eclipse
    >>> 3) Start Eclipse as a non-admin user
    >>> At this point Eclipse works OK. It will use ~/.eclipse/ for user-
    >>> based config files
    >>> 4) Install WOLips using the Software Manager in Eclipse
    >>> Eclipse will fail to start when restarted at the end of the
    >>> installation of WOLips
    >>>
    >>> Here is what works:
    >>>
    >>> 1) Install Eclipse 3.4.2 into e.g. /Developer/Applications/eclipse
    >>> 2) Change the ownership of the install folder to your account (non-
    >>> admin joeuser)
    >>> chown -R joeuser:joeuser /Developer/Applications/eclipse
    >>> 3) Start Eclipse as joeuser
    >>> 4) Install WOLips using the Software Manager in Eclipse
    >>> At this point Eclipse works OK.
    >>> It will NEVER use ~/.eclipse/ for user-based config files.
    >>> The folder ~/.eclipse/ is not even created.
    >>>
    >>> Thanks for trying to reproduce this. I appreciate it.
    >>>
    >>> Best regards
    >>> Rudy
    >>>
    >>>
    >>>
    >>> On Jun 19, 2009, at 2:47 PM, Q wrote:
    >>>
    >>>>
    >>>> On 19/06/2009, at 4:32 PM, Rudolf B. Blažek wrote:
    >>>>
    >>>>> That is the point --- it does NOT work with 3.4.2
    >>>>
    >>>> Ok, just verifying that when 3.4.2 is installed manually (as
    >>>> opposed to using the AIO installer) it still fails.
    >>>>
    >>>> I will try to reproduce the problem when I get a chance.
    >>>>
    >>>>> On Jun 19, 2009, at 2:06 PM, Q wrote:
    >>>>>
    >>>>>>
    >>>>>> On 19/06/2009, at 2:59 PM, Rudolf B. Blažek wrote:
    >>>>>>
    >>>>>>>
    >>>>>>> B) If several users need to use Eclipse with WOLips, use
    >>>>>>> Eclipse 3.4.1
    >>>>>>> --- Install Eclipse 3.4.1 into e.g. /Developer/Applications/
    >>>>>>> eclipse
    >>>>>>> --- Change the ownership of the install folder to root:admin
    >>>>>>> chown -R root:admin /Developer/Applications/eclipse
    >>>>>>> --- Install WOLips using the Software Manager in Eclipse
    >>>>>>> --- Eclipse 3.4.1 will use the ~/.eclipse folder correctly,
    >>>>>>> AFAIK
    >>>>>>
    >>>>>> Does this technique not work with 3.4.2?
    >>>>>>
    >>>>>> --
    >>>>>> Seeya...Q
    >>>>>>
    >>>>>> Quinton Dolan - qdola..mail.com
    >>>>>> Gold Coast, QLD, Australia (GMT+10)
    >>>>>> Ph: +61 419 729 806
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>>
    >>>>
    >>>> --
    >>>> Seeya...Q
    >>>>
    >>>> Quinton Dolan - qdola..mail.com
    >>>> Gold Coast, QLD, Australia (GMT+10)
    >>>> Ph: +61 419 729 806
    >>>>
    >>>>
    >>>>
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Fri Jun 19 2009 - 08:20:26 EDT