Re: Classpath problems

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Tue Feb 17 2004 - 04:51:58 EST

  • Next message: Ulrich Köster: "Re: WOLips for 3M7"

    Hi Emmanuel,

    M7 has a lot of performance fixes. Anyway you can group your projects
    in different workspaces.

    Ulrich

    Am 16.02.2004 um 14:06 schrieb Harald Niesche:

    > Koch Emmanuel wrote:
    >> Hi Ulrich,
    >> I found the new integration build of eclipse too slow. So slow that
    >> it is unusable for us.
    >> I don't know why it is so slow, but with my 50 frameworks, I can't
    >> use it.
    >> I'm trying now the new WOLips version with the eclipse3M6 stable
    >> build.
    >> It works better, but I have the following problem with your
    >> instructions :
    >> When I close a project, the dependencies of the other frameworks
    >> linked to this one are broken, and they don't build anymore.
    >> As I don't work on all my frameworks at the same time, I don't need
    >> to keep them in memory (and in the others process queues).
    >> When I was usign the classpath with the jars, I was able to close all
    >> projects without keeping the other frameworks from compiling.
    >> Must I keep all my frameworks open now during work, or is there an
    >> other solution?
    >
    > If your application requires all those Frameworks and you want to
    > close them, consider installing them somewhere (preferably
    > LOCAL_ROOT/Frameworks or whatever it's called) and reference them
    > using the ClasspathContainer (Add Library ... WO Frameworks).
    >
    > Otherwise you are right, projects that are on the build path need to
    > be open in order for Eclipse to be able to compile things that depend
    > on them.
    >
    > Harald
    >
    >



    This archive was generated by hypermail 2.0.0 : Tue Feb 17 2004 - 04:52:04 EST