To answer your questions, yes, I am running it from the build directory
and yes, the ant.jar is present there.
I made a quick change to the build-turbine.sh based on the old one.
Basically I changed the generated command line at the end and that is
all I altered.
-${JAVA_HOME}/bin/java org.apache.tools.ant.Main -buildfile ${BUILDFILE}
"$@"
+${JAVA_HOME}/bin/java -classpath ${CLASSPATH} -DJAVAC=${JAVAC}
org.apache.tools.ant.Main -buildfile ${BUILDFILE}
"$@"
I don't have my classpath set at all and have been letting the turbine
build script set it. However, every indication was that the classpath
was being ignored. So I just explicitly put the classpath on the command
line and the build runs. This led me to make a different change.
First I restored the command line to its original state and then
exported CLASSPATH inside the build-turbine.sh script. This also works.
Do you have your classpath preset as an environment variable in your
shell? Should I do the same or should the CLASSPATH be exported in the
script for other applications to inherit? Being unfamiliar with what
your goals were here with this build cleanup I am inclined to think it
should be exported in the script.
Thanks again,
David Ramsey
Christopher Elkins wrote:
>
> > I did not check on the CVS over the weekend so am not sure when this
> > occurred but since yesterday I have seen the following situation. When
> > I do a CVS update for turbine in Win98 and do a build, all builds fine.
> > When I attempt the same thing from my Linux installations I get:
> >
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > org/apache/tools/ant/Main
> >
> > I've done this on two separate Win98 installations, one with JDK 1.2.2
> > and another with 1.3. Both worked. I also have two separate Linux
> > installations, each with the same JDKs and both fail in the same way. I
> > am unsure what is happening here since the ant.jar file is there and
> > contains its Main.class file and the ant.jar is getting added to the
> > classpath in the build-turbine.sh script. I am aware that there was some
> > major cleanup of the build process.
> >
> > Has anyone else seen this? Any suggestions on how to get around it?
> >
> I was the one that did that clean-up, but I just built it fine on my Linux box.
> Here's the relevant parts of my environment:
> Linux 2.2.14-5.0.14c
> Java version "1.2.2"
> Classic VM (build 1.2.2_006, green threads, nojit)
>
> Gosh. The only things I can think of are the basics: Are you running
> ./build-turbine.sh from inside turbine/build? Is ant.jar actually in that
> directory? Is there anything else in your CLASSPATH?
>
> > Thanks,
> > David Ramsey
> > --
>
> --
> Christopher Elkins
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
--
==============================================================
"Always listen to experts. They'll tell you what can't be
done, and why. Then do it."
-- Lazarus Long, in Robert Heinlein's Time Enough for Love
==============================================================
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
