CVS and Subversion support keyword setting: Like CVS, Subversion supports keywords that can be expanded in files, such as $Id$, $Date$, $Revision$, etc. By default, these properties (svn:keywords) are not set on files [http://www.middleware.vt.edu/doku.php?id=middleware:subversion].
Could I use one of these keywords like the one for version id $Id$ and maybe %revision$ in the "currentVersion" element of my project.xml files so that the version numbering is driven by Subversion rather than me trying to keep the Subversion version number in sync with my Maven version number? Thanks, Ken -----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Friday, September 30, 2005 12:53 PM To: Maven Users List Subject: Re: Versioning Ken, Could you elaborate more in "one place"? like in one pom, and have all sub poms to inherite it? If so, you are not alone. Currently, you have to declare at least the parent's pom version for each sub pom. I doubt you can get away not tagging the SCM. without the tag, you can't retreive the exact source to reproduce the artifact. Hope it helps. -D On 9/30/05, Ballard, Ken <[EMAIL PROTECTED]> wrote: > > I'd like to only declare a version number in one place. Given the > opportunity, we'll mix them up at some point if the potential exists. > I'd rather not have to tag it with a version number in our SCM and > give it a version number in Maven. I'd like to only worry about > incrementing the version number in one place. Can that be done? > > Thanks, > > Ken Ballard > > DFS Java Team Lead, NCLeads > > ACS Government Healthcare Solutions > > 919.855.5756 > > --------------------------------------------------------------------- > 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]