On Fri, 28 Nov 2003, Rankin, SE (Stephen) wrote:
> I am having difficulty starting any of the STARJAVA applications
> [ussc@saturn bin]$ ./treeview
> Exception in thread "main" java.lang.NoClassDefFoundError:
> uk/ac/starlink/util/Loader
> at uk.ac.starlink.treeview.Driver.main(Driver.java:32)
>
> is this related to util?
No, it just means that you have a broken installation (the util.jar file
isn't installed or where expected), or that the treeview script isn't
using the correct CLASSPATH (only way that could happen is if you have a
TREEVIEW_DIR variable set, which you shouldn't).
> Note, I think there is some confusion (at least on my part) on some of the
> properties in the build.xml files. In .stardev.properties I set,
>
> star.dir=/apps/cvsbuild/star
> star.install=/apps/cvsbuild/starjava
> star.jar.dir=/apps/cvsbuild/starjava/lib
> star.archive.dir=/apps/cvsbuild/export
> stardev=/apps/cvsbuild/star
> perl=/usr/bin/perl
>
> What I am particularly confused about is star.jar.dir, in all of the
> build.xml files it is set to ${star.dir}/lib, but isn't ${star.dir} supposed
> to point to the Classic Starlink?
No. It should point at the "starjava" directory so I'd use:
star.dir=/apps/cvsbuild/starjava
star.archive.dir=/apps/cvsbuild/export
stardev=/apps/cvsbuild/star
perl=/star/bin/perl
and leave the rest alone. They are for quite fine tuning. In general the
properties using in the Java build system apply to it and have very little
to do with the classic system (the exceptions being Perl and where the JNI
using packages can pick up the libraries they need to link against).
> If you chose to install in a different
> location set by star.install then star.jar.dir will point to the wrong
> location. This affects the HDX test, which fails in a different way if I
> don't set star.jar.dir in .stardev.properties.
I think you setting this independently of "star.dir" is probably causing
this issue.
Cheers,
Peter.
|