Relase plugin batch mode: http://maven.apache.org/plugins/maven-release-plugin/examples/non-interactive-release.html
/Anders On Wed, Nov 25, 2009 at 13:52, Jeff French <j...@mdbconsulting.com> wrote: > > Thanks, Anders. I guess you could call it a nightly release. The version > numbering scheme is major.minor.patch.build, so while working on a given > version, the build component would increase each night. > > I looked at the release plugin, but it appears to require some manual > involvement, and I'd like this process to be completely automated. Also, it > tags the sources in scm, but our build server already handles that part. > > I will take a look a the plugin's source, though, to see if makes sense to > base a custom plugin off of it, or if I'm missing something in how it is > used. > > Jeff > > > Anders Hammar wrote: > > > > Looks to me that what you're doing is a release build, not a nightly > build > > (at least not what I associate with the "nightly build" expression". You > > should take a look at the release plugin: > > http://maven.apache.org/plugins/maven-release-plugin/ > > > > It will release your project including updating the version correctly and > > set a label in your scm. > > > > /Anders > > > > On Wed, Nov 25, 2009 at 05:29, Jeff French <j...@mdbconsulting.com> > wrote: > > > >> > >> I'm trying to replicate our Maven-1 nightly build/deploy process with > >> Maven-2. Basically, a build server passes the current version to a maven > >> process that then produces artifacts with that version number appended. > >> > >> Since the build occurs on the same machine as the repo, I'm guessing I > >> can > >> perform an 'install' instead of a 'deploy'. I've found that this: > >> > >> mvn -Dversion=1.1.1 install > >> > >> will produce numbered artifacts if the pom contains these snippets: > >> > >> <project> > >> ... > >> <version>${version}</version> > >> > >> <properties> > >> <version>1.1-SNAPSHOT</version> > >> </properties> > >> ... > >> </project> > >> > >> The problem is the reposed .pom files contain the ${version} string > >> instead > >> of the defined version (1.1.1). Is there any way for the deployed pom to > >> be > >> the result of filtering the build pom with the defined system property? > >> Or > >> more importantly, is there a better way to go about what I'm trying to > >> achieve? > >> > >> Thanks for any pointers. > >> > >> Jeff > > > > -- > View this message in context: > http://old.nabble.com/Subject%3A-Adding-version-numbers-to-artifacts-tp26507407p26512100.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
