Most of the jar files are only a few hundred k - could they be stored as
blobs of some form in a database which the jjar server queries?
> -----Original Message-----
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 08 August 2001 5:24 pm
> To: [EMAIL PROTECTED]
> Subject: Re: Version numbers on release JARs
>
>
> Jason van Zyl wrote:
> >
> > Is there a reason why we're not placing the version number
> in the name of
> > the JAR. I am trying to use a central repository of JARs
> for building all
> > turbine projects and I know I will eventually run into a
> case where I need
> > to store different versions of a package in the same directory.
> >
> > I know the version informatin is in the manifest, but you
> can't store
> > multiple versions of packages in the same directory right now.
>
> IMHO, placing all the jars from disparate projects into a
> single directory
> produces a mess. Pop quiz: where does optional.jar come
> from? That was an
> easy one, eh? How about mail.jar? roles.jar? utils.jar?
> runtime.jar?
> These are real names actually in use.
>
> A better approach is to organize the jars into directories.
> The names of
> those directories can contain version information, etc. And separate
> README and LICENSE files...
>
> - Sam Ruby
>
=======================================================================
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission. There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
