version.name was never meant to have anything to do with cvs. It is there to hold the rather arbitrary name of a release (ie. rabbit-hole or whistler or merlin). While understand your desire to include cvs tag information, I do not think that this is the best place for it.
I suggest we add a version.cvstag for this purpose. This is currently onlyt being used to generate the spec and impl bits for mf files right? --jason On Sun, 2002-02-17 at 07:44, Scott M Stark wrote: > User: starksm > Date: 02/02/17 07:44:38 > > Modified: jboss build.xml > Log: > Document the use of version.name as the cvs tag for any release build > > Revision Changes Path > 1.85 +2 -1 build/jboss/build.xml > > Index: build.xml > =================================================================== > RCS file: /cvsroot/jboss/build/jboss/build.xml,v > retrieving revision 1.84 > retrieving revision 1.85 > diff -u -r1.84 -r1.85 > --- build.xml 17 Feb 2002 15:07:14 -0000 1.84 > +++ build.xml 17 Feb 2002 15:44:38 -0000 1.85 > @@ -12,7 +12,7 @@ > <!-- --> > <!-- ====================================================================== --> > > -<!-- $Id: build.xml,v 1.84 2002/02/17 15:07:14 starksm Exp $ --> > +<!-- $Id: build.xml,v 1.85 2002/02/17 15:44:38 starksm Exp $ --> > > <project default="main" name="JBoss/Build"> > > @@ -65,6 +65,7 @@ > <property name="version.minor" value="0"/> > <property name="version.revision" value="0"/> > <property name="version.tag" value="beta"/> > + <!-- This must be set to the CVS tag for any release --> > <property name="version.name" value="Rel_3_0_0_3"/> > > <!-- Module name(s) & version --> > > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
