On Fri, 26 Sep 2003, David Berry wrote:
> Dear All,
> This message follows on from a discussion I have been having with
> Mark and Steve. I've not really been involved in the development or
> distribution of any of STARJAVA, so I'm coming to this pretty much stone
> cold. I wanted to add something to the AST home page to advertise the
> fact that it can be used from java via JNIAST. Obviously, one hopes that
> other people may use JNIAST/AST within their own Java applications. In
> this case they probably want to download JNIAST plus its dependancies, but
> may well not want to download all the other STARJAVA stuff (TreeView,
> Splat, HDX, etc). Mark's reply suggested that downloading individual
> components of STARJAVA was not, in general, possible.
>
> Firstly, apologies to Mark if I have misunderstood him, but if not,
> shouldn't we be very worried about this? It seems to me very important
> that people should be able to download just the bits of STARJAVA which
> they want. Getting the entire works when they only want a small part will
> be a big turn-off. Imagine if this was the case for classic starlink!
> "I want to use the CHR library, do I really need also to have KAPPA,
> FIGARO, GAIA, CCDPACK, etc, etc, etc?".
Hi David,
each package has its own export targets so they can be individually
separated, just like for each classic package. However, we currently don't
offer this level of separation in a released form.
> Steve made a point about the difficulty of determining the dependancies
> of each individual component. If this is a problem, isn't it something
> we need to address?
It may be problematic, but the required information is there. At sometime
we need a tool to track down the dependencies of an application jar file
(I have done most of this task in ANT) so we can see this explicity and
arrange to pick up the necessary parts.
Peter.
|