Ok, I uninstalled, upgraded to 1.0.1 (thanks guys – I had been using
1.0.0 beta something), and I did the steps you mentioned, and then
removed the built .woa, rebuilt all again, closed the project then
opened it, and then it worked.
I was about to sacrifice a chicken, drop it’s blood on my keyboard, and
dance nude by the moonlight, but now I won’t have to go through the
hassle.
;)
Thanks for the help.
I have a further question, which may have been answered, but I can’t
find it. I have used substantial number of files that in production are
located in
LOCALROOT/Library/Webobjects/Extensions/*.jar (axis, etc.)
I have then linked in my build properties. Do I need to make them host
off of NEXT_LOCAL_ROOT to actually show up in UNIXClasspath.txt?
Cg.
-----Original Message-----
From: Ulrich Köster [mailto:ulric..bjectstyle.org]
Sent: Wednesday, April 30, 2003 1:21 PM
To: Christian Gruber
Cc: 'Pierre Bernard'; woproject-de..bjectstyle.org
Subject: Re: Order of classpath entries in *ClassPath.txt file
Hi,
Make sure that the variables are created. If they are there just try a
rebuild all.
Ulrich
Am Mittwoch, 30.04.03 um 18:51 Uhr schrieb Christian Gruber:
Ok, I just did this, and now I can’t build any of my projects due to
“unresolved classpath variables”.
??
Cg.
-----Original Message-----
From: Ulrich Köster [mailto:ulric..bjectstyle.org]
Sent: Wednesday, April 30, 2003 11:54 AM
To: Christian Gruber
Cc: 'Pierre Bernard'; woproject-de..bjectstyle.org
Subject: 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/Reso
urces/Java/javajdbcadaptor.jar"/>
<classpathentry kind="var"
path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaWebObjects.framework/Resou
rces/Java/javawebobjects.jar"/>
<classpathentry kind="var"
path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaEOControl.framework/Resour
ces/Java/javaeocontrol.jar"/>
<classpathentry kind="var"
path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaEOAccess.framework/Resourc
es/Java/javaeoaccess.jar"/>
<classpathentry kind="var"
path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaWOExtensions.framework/Res
ources/Java/JavaWOExtensions.jar"/>
<classpathentry kind="var"
path="NEXT_SYSTEM_ROOT/Library/Frameworks/JavaFoundation.framework/Resou
rces/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/Ja
va/javaxml.jar"/>
<classpathentry kind="src" path="/org.postgresql"/>
<classpathentry kind="var"
path="NEXT_LOCAL_ROOT/Library/Frameworks/PostgresqlPlugIn.framework/Reso
urces/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
This archive was generated by hypermail 2.0.0 : Thu May 01 2003 - 10:45:49 EDT