Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixup how to maven release after my experience sitting by Lars -- there was a critical piece missing from the doc 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1480163 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2013-05-08 05:47:01 +00:00
parent 6f79d0e253
commit 2273a939e2
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/main/docbkx/developer.xml
View File

@ -205,9 +205,11 @@ mvn clean package -DskipTests
865 ~/bin/mvn/bin/mvn release:prepare 865 ~/bin/mvn/bin/mvn release:prepare
866 # Answer questions and then ^C to kill the build after the last question. See below for more on this. 866 # Answer questions and then ^C to kill the build after the last question. See below for more on this.
867 vi release.properties 867 vi release.properties
# Change the references to trunk svn to be 0.92.2mvn; the release plugin presumes trunk # Change the references to trunk svn to be 0.92.2mvn. The release plugin presumes trunk.
# Then restart the release:prepare -- it won't ask questions # Where it asks for a label for the release specify a label that does not yet exist; e.g.
# because the properties file exists. # 0.92.2mvn2 (i.e. add a character, here a '2', to the label you are currently working
# against so when maven goes to label the release, it does not clash with an existing one).
# Then restart the release:prepare -- it won't ask questions because the properties file exists.
868 ~/bin/mvn/bin/mvn release:prepare 868 ~/bin/mvn/bin/mvn release:prepare
# The apache-release profile comes from the apache parent pom and does signing of artifacts published # The apache-release profile comes from the apache parent pom and does signing of artifacts published
869 ~/bin/mvn/bin/mvn release:perform -Papache-release 869 ~/bin/mvn/bin/mvn release:perform -Papache-release