On Thu, 21 Mar 2002, Immanuel, Gidado-Yisa wrote:
> Date: Thu, 21 Mar 2002 13:21:34 -0500
> From: "Immanuel, Gidado-Yisa" <[EMAIL PROTECTED]>
> Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
> To: 'Jakarta Commons Developers List' <[EMAIL PROTECTED]>
> Subject: RE: property naming (Re: cvs commit: jakarta-commons/digester
> bui ld.properties.sample)
>
>
> > -----Original Message-----
> > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, March 21, 2002 12:36 PM
> ...
> > commons-collections.jar=${commons-collections.home}/commons-co
> > llections.jar
> > commons-logging.home=../logging/dist
> > commons-logging.jar=${commons-logging.home}/commons-logging.jar
> > junit.home=/usr/local/junit3.7
> > junit.jar=${junit.home}/junit.jar
> >
> > So, the proposal would be to change this to the following:
> >
> > commons-collections.jar=${lib.repo}/commons-collections.jar
> > commons-logging.jar=${lib.repo}/commons-logging.jar
> > junit.jar=${lib.repo}/junit.jar
>
> Could you use naming conventions like:
>
> commons-collections.jar=${lib.repo}/commons-collections_1.2.jar
>
> to refer to the explicit version (1.2 in this case) of the jar?
> Whereas, the following line:
>
> commons-collections.jar=${lib.repo}/commons-collections.jar
>
> would mean you're using the latest and greatest build (probably
> something built off of CVS MAIN, but *not* a symlink to a
> versioned jar)?
>
As long as the Ant property names themselves do not include the version
numbers, the scheme would accomodate filenames that do. But, for the
defaults (i.e. in build.properties.sample) the unversioned version of the
names should be used.
Personally, I think version numbers belong inside the JAR (in the
META-INF/MANIFEST.MF file) where tools can get to them reliably, rather
than in the filename itself, where users can easily mess them up. It
should be up to a repository system (JJAR, Maven, whatever) to grab me
version x.y of foo.jar when I ask for it.
But the naming convention works either way.
> - Gidado
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
