----- Original Message -----
From: "Jason van Zyl" <[EMAIL PROTECTED]>
To: "Vincent Massol" <[EMAIL PROTECTED]>
Sent: Wednesday, August 08, 2001 4:45 PM
Subject: Re: Version numbers on release JARs
> On 8/8/01 11:23 AM, "Vincent Massol" <[EMAIL PROTECTED]> wrote:
>
> >
> > ----- Original Message -----
> > From: "Jason van Zyl" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 08, 2001 4:13 PM
> > Subject: Version numbers on release JARs
> >
> >
> >> Hi,
> >>
> >> 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.
> >>
> >
> > The only reason I can think of is that it is a pain to have to change
all
> > the places which references a given jar when you upgrade to a new
version
> > ...
>
> That's a good point. What I'm basically trying to do is make a build
system
> where the dependencies are satisfied by automatically downloading what is
> missing. Right now I have a single directory with a series of JARs
contained
isn't this the jjar, cjan, ... idea that we have discussed several times on
this list in the past ?
I seem to remember Scott Sanders (or Geir or both) even put the beginning of
an implementation in the sandbox.
> within but I could easily adapt this to be a directory that contains a
> directory for each package and within that a directory for each version:
>
> lib.repo/
> -> velocity
> -> 1.1
> -> 1.2
> -> turbine
> -> 2.1
> -> 3.0
>
> Is this what you had in mind?
yes, as a first and simple approach.
>
> > Also you should think about nightly builds. Certainly the nighlty builds
> > will have no version in the name of the jar or if it had it would change
> > every day (which is even more difficult to manager from places where it
is
> > referenced).
>
> Yes, I agree that a standard name for a jar would make maintaining build
> files easier.
>
> > Create directories or better, instead of using a standard file system,
use a
> > versioned one (like a SCCS: CVS or something like iFS from Oracle, or
Slide
> > ...).
>
> I'm trying to avoid putting JARs in CVS if that's what you mean.
What I mean is a solution is to use a versioned file system, whatever that
be, i.e. you can query a file by asking by name and also passing in a
version (like CVS actually). Slide (http://jakarta.apache.org/slide/) could
do that. However it is probably too complicated for what you have in mind at
the current time. What is the problem with using CVS for that ?
-Vincent
