From 1df1ea3d1af372a4a4e5e1e03467fd41439baf49 Mon Sep 17 00:00:00 2001 From: Jason van Zyl Date: Mon, 11 Jul 2005 03:06:36 +0000 Subject: [PATCH] o this release guide is really just a place holder and contains the couple of commands i need for releasing :-) git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@210060 13f79535-47bb-0310-9956-ffa450edef68 --- maven-site/src/site/apt/guides/releasing.apt | 35 ++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 maven-site/src/site/apt/guides/releasing.apt diff --git a/maven-site/src/site/apt/guides/releasing.apt b/maven-site/src/site/apt/guides/releasing.apt new file mode 100644 index 0000000000..da83fdfc3f --- /dev/null +++ b/maven-site/src/site/apt/guides/releasing.apt @@ -0,0 +1,35 @@ + ----- + Releasing + ----- + The Maven Team + ----- + +Releasing + + The release plugin provides some basic functionality for making releases, and updating + the project SCM accordingly. A release is performed in 2 steps: + + [[1]] Preparing the release. + + [[2]] Performing the release. + +Preparing the release + + The <<>> goal will: + + [[1]] Verify that there are no uncommitted changes in the checkout + [[2]] Prompt for a desired version and tag name + [[3]] Modify the pom.xml + [[4]] Tag the entire source tree with the new tag name + +----- +m2 release:prepare -DtagBase=svn+ssh://svn.codehaus.org/home/projects/plexus/scm/tags +----- + + When this operation is over, your source control has the released code tagged and ready to deploy. + +Performing the release + +----- +m2 release:perform -DtagBase=svn+ssh://svn.codehaus.org/home/projects/plexus/scm +-----