[jdom-interest] [PATCH] wrong jar version

[Bradley S. Huffman]

If you want to carry it a step further and change @version in all the 
java files to the RCS id's $Revision$, $Date$, I made a patch this
morning.

It's at ftp://a.cs.okstate.edu/pub/hip/jdom-version.patch if you want it.

Brad

Jason Hunter writes:

> Excellent suggestions.  I've integrated your patch.
> 
> -jh-
> 
> Jeff Turner wrote:
> > 
> > Hi,
> > 
> > Currently, any 'jdom.jar' built from CVS will claim that it is beta 7,
> > when one interrogates it via 'java -jar'. This effectively renders the
> > whole version reporting system useless, as a jdom.jar from 6 months ago
> > look exactly like one produced yesterday.
> > 
> > This may be a symptom of a deeper misunderstanding. Is "beta 7" a point
> > in time, or an ongoing period of time (about 6 months)? Are we "in the
> > 7th beta", or has it been and gone?
> > 
> > I'll assume a beta is a "point in time", as this is what users believe,
> > and the website indicates ("JDOM Beta 7 was released!").
> > 
> > In which case, some terminology is needed for where JDOM is, now.
> > 
> > The attached patch adopts the <next version>-dev approach. Once applied,
> > 'java -jar jdom.jar' will report:
> > 
> > JDOM version 1.0beta8-dev, built January 6 2002
> > Copyright 2000-2001, Jason Hunter and Brett McLaughlin
> > ...
> > 
> > Does that sound reasonable?
> > 
> > If so, the implication is that when beta 8 arrives, the distro builder
> > must update the version flag to "beta 8", do the build, then immediately
> > change the flag to "beta 9-dev".
> > 
> > thanks,
> > 
> > --Jeff
> > 
> >   ------------------------------------------------------------------------
> > 
> >    versioning.patchName: versioning.patch
> >                    Type: Plain Text (text/plain)
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost
> .com