Howdy, You could have a common header jsp that's included in pages, which gets the version number from a servlet context parameter, or a property file. JNDI is too heavyweight for this I think. The purely ant approach is alright.
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Euan Guttridge [mailto:[EMAIL PROTECTED] >Sent: Friday, October 10, 2003 8:29 AM >To: 'Tomcat Users List' >Subject: RE: OT How to maintain a version number > >Easy if you build with ANT - but very OT! Use the increment task to >increment a property file, then a filterset to place that version number >into a JSP/HTML. For more info email me direct or post to ANT mailing list. > >Euan > >-----Original Message----- >From: Koes, Derrick [mailto:[EMAIL PROTECTED] >Sent: 10 October 2003 13:22 >To: 'Tomcat Users List' >Subject: RE: OT How to maintain a version number > > >Property file? > >-----Original Message----- >From: Jim Lynch [mailto:[EMAIL PROTECTED] >Sent: Friday, October 10, 2003 8:17 AM >To: Tomcat Users List >Subject: OT How to maintain a version number > >I've written an application where I need to keep up with the version >number. I'm trying to figure out an elegant way to maintain that in the >simplest and perhaps the most automated way. My source is kept in a cvs > archive but of course there are dozens of files so it would be >difficult to base a version number on the version number of a single >source or would it? > >The number would be displayed as part of the title(<TITLE> My App >0.92</TITLE>) in the index.jsp so it would have to be easily available >to that file. I suppose I could use JNDI, I could hardwire it into the >index.jsp file, but I probably want to put it into other .jsp files also >and it would be harder to keep up with that way. > >Anyway I'm looking for good ideas from this very enlightened crowd. > >Thanks, >Jim. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >This electronic transmission is strictly confidential to Smith & Nephew and >intended solely for the addressee. It may contain information which is >covered by legal, professional or other privilege. If you are not the >intended addressee, or someone authorized by the intended addressee to >receive transmissions on behalf of the addressee, you must not retain, >disclose in any form, copy or take any action in reliance on this >transmission. If you have received this transmission in error, please >notify the sender as soon as possible and destroy this message. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
