Re: Can't open workspace

From: Chuck Hill (chil..lobal-village.net)
Date: Mon Mar 17 2008 - 13:48:37 EDT

  • Next message: Chuck Hill: "Re: source control best practice with wonder"

    On Mar 17, 2008, at 10:45 AM, Xavier Destombes wrote:

    > Hello Chuck,
    >
    >>> Hi,
    >>>
    >>> I've just reinstalled Leopard...
    >>> Eclipse/WOLips is working correctly until I change my frameworks
    >>> to be 53 instead of 54.
    >>
    >> How are you doing that? Using a pretty modern (the new stable or a
    >> bit newer) of WLips, I just define this property:
    >>
    >> wo.wosystemroot=/Users/chuck
    >>
    >> and copy the 5.3 frameworks into /Users/chuck/Library/Frameworks.
    >> The 5.4 frameworks are left unmolested in /System/Library/
    >> Frameworks. If I want 5.4, I just change this to
    >>
    >> wo.wosystemroot=/
    >
    > Sounds good to me:) where did you put this property? in the
    > Properties file for the application or there's a way to make it
    > global at least for a specific workspace?

    I have a custom build, I set it very early in the process:

          <target name="load.properties">

                   <!-- Hack to use WO 5.3.3 on Leopard, remove when good 5.4
    released -->
              <property name="wo.wosystemroot"
                        value="${user.home}"/>

              <property file="build.properties"/>

    You could also set it in ~/Library/Frameworks/wobuild.properties.

    Chuck

    >>> I'm back with the swt error and so on...
    >>>
    >>> Is there any way I can have Eclipse/WOLips working with 53 on
    >>> development? or something else I should do after changing my
    >>> frameworks to 53.
    >>
    >> It works for me.
    >>
    >>
    >> Chuck
    >>
    >>
    >>>> Thanks, I'll try that at the end of the week, I've install a
    >>>> clean Leopard on an external hard drive, I'll try to find what's
    >>>> causing the issue...
    >>>>
    >>>>
    >>>>
    >>>>>>>> Your'e right, I've re-open the faulty workspace to get the
    >>>>>>>> latest stack trace, maybe it's more helpful:)
    >>>>>>> Are there any other errors in this log? And when you say it
    >>>>>>> crashes a couple seconds later, can you explain what you
    >>>>>>> mean? Does the app just disappear, do you get an exception
    >>>>>>> dialog? If the app just disappears, that sounds like a native
    >>>>>>> crash, not a Java crash, and if so, is there a system crash
    >>>>>>> log for it?
    >>>>>>
    >>>>>> Well no, if I try to reopen, I get the same error.
    >>>>>> The app just disappear.
    >>>>>> I can see the workbench like 2-3 seconds (but no project is
    >>>>>> displayed), then the app just disappear.
    >>>>> That SWT "No more handles" thing is more likely to be related,
    >>>>> but even though really shouldn't crash Eclipse. But I put a new
    >>>>> nightly build up that maybe will prevent that error (it won't
    >>>>> fix the underlying problem, it will just prevent the explosion).
    >>>>>
    >>>>> ms
    >>>>>
    >>>>>
    >>>>
    >>>>
    >>>
    >>>
    >>
    >> --
    >>
    >> Practical WebObjects - for developers who want to increase their
    >> overall knowledge of WebObjects or who are trying to solve specific
    >> problems.
    >> http://www.global-village.net/products/practical_webobjects
    >>
    >>
    >>
    >>
    >>
    >>
    >
    >

    -- 
    

    Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects



    This archive was generated by hypermail 2.0.0 : Mon Mar 17 2008 - 13:50:20 EDT