David,
I think now that it should be relatively easy to separate STARJAVA into
libraries/infrastructure and applications. But for the matter of a few
megabytes at the moment, I would say just take the lot. The ability to
export an individual jar file for an application also extends to libraries
and source; sorry I should have said that.
The nightly build for Linux (RedHat 9.0) is on Saturn. You can login to
Saturn and get the latest built version from the directory.
/apps/cvsbuild/export
A zip file for the sources is also available in that directory.
The exports get updated every night, or not if the cvs checkout didn't build
(just check that date of the files).
Steve.
-----Original Message-----
From: David Berry [mailto:[log in to unmask]]
Sent: 26 September 2003 16:49
To: [log in to unmask]
Subject: Re: Obtaining individual components of STARJAVA
Steve,
On Fri, 26 Sep 2003, Rankin, SE (Stephen) wrote:
> Mark has the best idea, disable the features within an
> application if the other components are unavailable. This would be a good
> way of reducing the sticky lump problem for STARJAVA. The only other way
> would be to include all the required components (i.e. individual class
> files) for an application in its jar file.
It's not just applications. People may want an individual class. As I say,
my specific concern is how people who have a casual interest in trying
out AST within their own Java applications can get the required files. If
it's not easy and quick, they won't bother. All they want is JNIAST and
its dependencies.
David
|