Re: Order of classpath entries in *ClassPath.txt file

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Wed Apr 30 2003 - 11:53:48 EDT

  • Next message: Ulrich Köster: "Re: Order of classpath entries in *ClassPath.txt file"

    Hi,

    I thought I answered the question. I try it with a longer answer:

    In versions prior to 0.9.8 we used the classpath variable NEXT_ROOT to
    resolve the NEXT_ROOT. To resolve problems with the LOCAL_ROOT we
    changed it NEXT_SYSTEM_ROOT and NEXT_LOCAL_ROOT.

    Both variables are created from values in the file
    $user.home/Library/wobuild.properites. To make sure they are in a
    correct format:
    1 Remove the NEXT_SYSTEM_ROOT and NEXT_LOCAL_ROOT classpath variables
    from the list of classpath variables under
    Window->Preferences->Java_Classpath Variables.
    2 Enable 'Rebuild wobuild.properties on next launch' in the wolips
    preferences.
    3 Quit Eclipse.
    4 Delete the wobuild.properties under $user.home/Library
    5 Relaunch Eclipse.

    Due to the change of the variables names you have to modify the
    .classpath files:
    <?xml version="1.0" encoding="UTF-8"?>
    <classpath>
         <classpathentry kind="con"
    path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
         <classpathentry kind="src" path="src"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaJDBCAdaptor.framework/
    Resources/Java/javajdbcadaptor.jar"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaWebObjects.framework/
    Resources/Java/javawebobjects.jar"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaEOControl.framework/
    Resources/Java/javaeocontrol.jar"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaEOAccess.framework/
    Resources/Java/javaeoaccess.jar"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaWOExtensions.framework/
    Resources/Java/JavaWOExtensions.jar"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaFoundation.framework/
    Resources/Java/javafoundation.jar"/>
         <classpathentry kind="lib" path="lib/junit.jar"/>
         <classpathentry kind="lib" path="lib/commons-logging.jar"/>
         <classpathentry kind="var"
    path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaXML.framework/Resources/
    Java/javaxml.jar"/>
         <classpathentry kind="src" path="/org.postgresql"/>
         <classpathentry kind="var"
    path="NEXT_LOCAL_ROOT/Library/Frameworks/PostgresqlPlugIn.framework/
    Resources/Java/PostgresqlPlugIn.jar"/>
         <classpathentry kind="output" path="bin"/>
    </classpath>

    You can also modify it in the java build bath properties page. This
    stuff is crossplatform.

    Ulrich

    Am Mittwoch, 30.04.03 um 17:26 Uhr schrieb Christian Gruber:

    > I still don’t think you answeredPierre’s last question (or did
    > you?). I’m still having this problem.
    >
    >  
    >
    > Christian.
    >
    >  
    >
    > -----Original Message-----
    > From: Ulrich Köster [mailto:ulric..bjectstyle.org]
    >  
    > BTW, on my Windows machine I see that with WOLips 1.0.0 the generated
    > UNIXClassPath.txt file contains full Windows file path (e.g.
    > D:\SomeFolder\...): This is not going to be good at deployment. Did I
    > do something wrong or is this a bug introduced between WOLips 0.9.7 &
    > 1.0.0?
    >

    This archive was generated by hypermail 2.0.0 : Wed Apr 30 2003 - 11:53:33 EDT