Re: Deadlock when adding a library to project java build path

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Tue Mar 16 2004 - 05:44:31 EST

  • Next message: Charles-Edouard Ruault: "Re: Deadlock when adding a library to project java build path"

    Am 15.03.2004 um 14:35 schrieb Charles-Edouard Ruault:

    > Hi all,
    >
    > i'm running into a consistent problem with WOLips, and 'im wondering
    > if this is a known problem.
    > I'm running Wolips 1.0.7.50 with eclipse 2.1.3RC3 on MacOS X 10.3.2.
    > Patched ant.core plugin.
    >
    > After adding existing projects ( Frameworks or Applications ) to the
    > workspace, i need to add some existing jars to the classpath ( log4j
    > for example ).
    > In order to do this, i use the following :
    >
    > Project -> Properties -> Java Build Path -> Libraries
    > Then i select Add Variable -> Extend -> NEXT_LOCAL_ROOT and then i
    > navigate the local filesystem to select the library.
    > When i click ok, the main dialog to close the "Properties" i'm getting
    > a progress information displaying "Setting build path, updating"
    > and eclipse is stuck there forever.
    > The only way to get out of this if to "Force Quit" eclipse.
    >
    > So the only way i found to add a libraries to the application path, i
    > have to manually edit the .classpath file located in the project root.
    > This is quite annoying ....
    >
    > Has anyone seen this ? any workaround / solution ?
    >
    > Thanks in advance for your help.
    > Regards
    >
    > PS: the same problem exists with eclipse 2.1.2 ( both on linux and
    > MacOSX ).

    RC3 has some issues. As a workaround use RC2.

    Ulrich



    This archive was generated by hypermail 2.0.0 : Tue Mar 16 2004 - 05:44:38 EST