Naming of jars in lib

["Peter B. West" <pb...@powerup.com.au>]

Fopdevs,

It might make life a little easier if library jars retained common names 
as we upgraded; ant.jar, for instance.  We have a many version-numbered 
jars in lib, the most particular of which is 
commons-io-dev-20030703.jar.  As we are all getting our libraries 
updated through CVS anyway, would it not be better to name them 
consistently, and include a text file detailing the current versions?

Peter
-- 
Peter B. West  http://www.powerup.com.au/~pbwest/resume.html


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Naming of jars in lib

[Clay Leeds <cl...@medata.com>]

On 7/11/2003 6:49 AM, Glen Mazza wrote:
> I don't think so--it is helpful to immediately see the
> version of the libraries when viewing the files.  I
> suspect that text file you're mentioning will out fall
> out of date--and users may be unaware of it.

I should preface this with: I've used CVS to submit *1* change, so I'm 
not exactly an expert here... ;-p

but...

Is it not possible to display the 'modified date' and/or 'version' in a 
separate column in CVS? I thought that was what 'Rev.' was for... I 
guess the 'Timestamp' relates to the time the item was added to the 
library, and not necessarily the file's 'modification date'. Hope this 
helps in some way...

> However, there *may* be an issue (I don't know, I
> haven't researched the matter) of the team not relying
> on production releases of other jars, but interim
> releases where unwarranted, nightly builds, etc.,
> which I would assume would make a mess in CVS due to
> the different file names, constant atticking, etc. 
> *That* might be something to work on:  attempting to
> rely on more production-release jars in the future.

...sounds messy... Don't forget to wash your hands afterwards...
-- 
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Naming of jars in lib

[Glen Mazza <gr...@yahoo.com>]

> As we are all getting
> our libraries 
> updated through CVS anyway, would it not be better
> to name them 
> consistently, and include a text file detailing the
> current versions?
> 
> Peter
> -- 

I don't think so--it is helpful to immediately see the
version of the libraries when viewing the files.  I
suspect that text file you're mentioning will out fall
out of date--and users may be unaware of it.

However, there *may* be an issue (I don't know, I
haven't researched the matter) of the team not relying
on production releases of other jars, but interim
releases where unwarranted, nightly builds, etc.,
which I would assume would make a mess in CVS due to
the different file names, constant atticking, etc. 
*That* might be something to work on:  attempting to
rely on more production-release jars in the future.

Glen

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org