You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by bu...@apache.org on 2014/03/06 09:53:41 UTC
svn commit: r900219 - in /websites/staging/isis/trunk: cgi-bin/ content/
content/contributors/release-process.html
Author: buildbot
Date: Thu Mar 6 08:53:40 2014
New Revision: 900219
Log:
Staging update by buildbot for isis
Modified:
websites/staging/isis/trunk/cgi-bin/ (props changed)
websites/staging/isis/trunk/content/ (props changed)
websites/staging/isis/trunk/content/contributors/release-process.html
Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 6 08:53:40 2014
@@ -1 +1 @@
-1574803
+1574806
Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 6 08:53:40 2014
@@ -1 +1 @@
-1574803
+1574806
Modified: websites/staging/isis/trunk/content/contributors/release-process.html
==============================================================================
--- websites/staging/isis/trunk/content/contributors/release-process.html (original)
+++ websites/staging/isis/trunk/content/contributors/release-process.html Thu Mar 6 08:53:40 2014
@@ -682,13 +682,21 @@ If you are working on Windows and using
<p>Run the dry-run as follows:</p>
-<pre><code>mvn release:prepare -P apache-release -D dryRun=true
+<pre><code>mvn release:prepare -P apache-release -D dryRun=true \
+ -Dtag=my-proj-1.2.3 \
+ -DreleaseVersion=1.2.3 \
+ -DdevelopmentVersion=1.2.4-SNAPSHOT
</code></pre>
<blockquote>
- <p>below there is details on how to run in batch (non-interative) mode.</p>
+ <p>The <code>--batch-mode</code> argument can also, in theory, be added, but it's not clear (to me at least) how to enter the passphrase in this case.</p>
</blockquote>
+<p>Or, f you want to be prompted for the versions, you can omit the properties, eg:</p>
+
+<pre><code>mvn release:prepare -P apache-release -D dryRun=true
+</code></pre>
+
<p>Some modules might have additional profiles to be activated. For example, the (now mothballed) SQL ObjectStore required <code>-P apache-release,integration-tests</code> so that its integration tests are also run.</p>
<p>This should generate something like:</p>
@@ -725,38 +733,32 @@ What is the release version for "Apache
1.2.3: :
</pre>
-<p>Then answer the next three questions. </p>
+<p>If you didn't provide the <code>tag</code>, <code>releaseVersion</code> and <code>developmentVersion</code> tags, then you'll be prompted for them:</p>
-<p>For the first, release version, you can generally accept the default; Maven just strips off the <code>-SNAPSHOT</code> suffix:</p>
+<ul>
+<li>For the first, release version, you can generally accept the default; Maven just strips off the <code>-SNAPSHOT</code> suffix:</li>
+</ul>
<pre>
-What is the release version for "Apache Isis Core"? (org.apache.isis.core:isis) 1.2.3: :
+ What is the release version for "Apache Isis Core"? (org.apache.isis.core:isis) 1.2.3: :
</pre>
-<p>For the next question, SCM release tag, you can generally accept the default. Maven's offered value is a concatenation of the <code>artifactId</code> and the version entered above <em>without a <code>-RCn</code> suffix</em>. This is the same as our <a href="release-branch-and-tag-names.html">standard</a>:</p>
+<ul>
+<li>For the next question, SCM release tag, you can generally accept the default. Maven's offered value is a concatenation of the <code>artifactId</code> and the version entered above <em>without a <code>-RCn</code> suffix</em>. This is the same as our <a href="release-branch-and-tag-names.html">standard</a>:</li>
+</ul>
<pre>
-What is SCM release tag or label for "Apache Isis Core"? (org.apache.isis.core:isis) isis-1.2.3: :
+ What is SCM release tag or label for "Apache Isis Core"? (org.apache.isis.core:isis) isis-1.2.3: :
</pre>
-<p>For the final question, new development version", the minor 'z' part of the version should be incremented, and <code>-SNAPSHOT</code> appended. Generally you can, once more, accept the default:</p>
+<ul>
+<li>For the final question, new development version", the minor 'z' part of the version should be incremented, and <code>-SNAPSHOT</code> appended. Generally you can, once more, accept the default:</li>
+</ul>
<pre>
-What is the new development version for "Apache Isis Core"? (org.apache.isis.core:isis) 1.2.4-SNAPSHOT:
+ What is the new development version for "Apache Isis Core"? (org.apache.isis.core:isis) 1.2.4-SNAPSHOT:
</pre>
-<p>If you don't want to avoid being prompted, you can also enter this information through properties, eg:</p>
-
-<pre><code>mvn release:prepare -P apache-release -D dryRun=true \
- -Dtag=my-proj-1.2.3 \
- -DreleaseVersion=1.2.3 \
- -DdevelopmentVersion=1.2.4-SNAPSHOT
-</code></pre>
-
-<blockquote>
- <p>The <code>--batch-mode</code> argument can also, in theory, be added, but it's not clear (to me at least) how to enter the passphrase in this case.</p>
-</blockquote>
-
<p>Assuming this completes successfully, delete the generated <code>release.properties</code> file:</p>
<pre><code>rm release.properties