Aha! I was hoping it did that. I must have misread the plugin specs. I'll look at the SCM plugin again. Thanks!
-----Original Message----- From: Doug Douglass [mailto:[EMAIL PROTECTED] Sent: Friday, September 30, 2005 2:17 PM To: Maven Users List Subject: Re: Versioning Ballard, Ken wrote: >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 > > > Ken, Unless I'm missing what you're trying to accomplish, doesn't the SCM plugin, in m1 at least, accomplish what you're after. When you execute maven scm:prepare-release, it prompts for a version and a tag and updates both the project.xml (currentVersion and versions) and SCM. If you could accomplish using the CVS keywords in currentVersion, do you really want every checkin of project.xml to produce new artifact versions? This seems a lot more problematic then just using a SNAPSHOT version until a release is ready, then using scm:prepare-release. DD --------------------------------------------------------------------- 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]
