On Fri, 26 Sep 2003, Rankin, SE (Stephen) wrote:
> The software store has build and runtime dependencies for the libraries, but
> only runtime dependencies for the applications. I have found in the past
> that the dependencies have been wrong, (build and runtime). I keep saying
> that I will check all the possible downloads, but haven't had the
> opportunity yet. I don't think that the dependencies have ever been checked
> since the store was first created! I suspect that they change with time and
> updates?
Hi Steve (David & Mark),
the maintenance of the dependencies is a problem, but, at least for the
STARJAVA system we do have a "handle" on it that forces us to keep things
up to date.
The handle is what jar files are referenced in the class-path of the main
jar file of an application or class library package. In the case of JNIAST
the main jar file manifest contains ../util/util.jar, which itself
currently refers to ../junit/junit.jar and ../ant.jar (!what's ANT doing
there!), both of which are deadends (no ../ relative parts in their
class-path manifests). So this tells us that JNIAST also needs the UTIL,
JUNIT and ANT packages.
The simplest way to manage this is therefore to extract this information
from the package build files (probably best to put this in a local file
that is read during the build and can be easily found/parsed by any
supporting process). Any takers to hack the (currently) 36 build files to
do this?
Peter.
|