You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by gi...@apache.org on 2020/05/01 16:21:46 UTC
[plc4x-website] branch asf-site updated: Site checkin for project
PLC4X: Jenkins Tools
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 516ef7a Site checkin for project PLC4X: Jenkins Tools
516ef7a is described below
commit 516ef7abc4d26b899b7ead06303de4c7faa1462e
Author: jenkins <bu...@apache.org>
AuthorDate: Fri May 1 16:21:42 2020 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/release/build-tools.html | 10 +++-------
developers/release/release.html | 14 +++++---------
2 files changed, 8 insertions(+), 16 deletions(-)
diff --git a/developers/release/build-tools.html b/developers/release/build-tools.html
index 6da8cdb..235f888 100644
--- a/developers/release/build-tools.html
+++ b/developers/release/build-tools.html
@@ -255,13 +255,9 @@ So please check <a href="release.html">here</a> (Chapters: <code>Preparing your
<p>Per default the plugin will ask for the working copy version during the build execution.
This is the version the <code>develop</code> branch will be changed to.</p>
</div>
-<div class="paragraph">
-<p>The parameter <code>autoVersionSubmodules</code> will tell the release plugin to release all modules with the same version.
-Otherwise we would have to define the working copy version for each module.</p>
-</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:branch -DbranchName=rel/code-generation/{minor-version} -DautoVersionSubmodules=true</pre>
+<pre>mvn release:branch -DbranchName=rel/code-generation/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -270,7 +266,7 @@ So in case of preparing the release branch for <code>{project.version}</code> th
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -DbranchName=rel/code-generation/0.7 -DautoVersionSubmodules=true</pre>
+<pre> mvn release:branch -DbranchName=rel/code-generation/0.7</pre>
</div>
</div>
<div class="paragraph">
@@ -363,7 +359,7 @@ In order to prepare a release-candidate, the first step is switching to the corr
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:prepare -DautoVersionSubmodules=true</pre>
+<pre>mvn release:prepare</pre>
</div>
</div>
<div class="paragraph">
diff --git a/developers/release/release.html b/developers/release/release.html
index e4bafbf..7ad13bd 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -247,7 +247,7 @@ Please be sure to execute the release with a Java version between 1.8 and 11 or
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DbranchName=rel/{current-short-version} -DautoVersionSubmodules=true</pre>
+<pre> mvn release:branch -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DbranchName=rel/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -262,7 +262,7 @@ Please be sure to execute the release with a Java version between 1.8 and 11 or
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:prepare -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DautoVersionSubmodules=true</pre>
+<pre> mvn release:prepare -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash</pre>
</div>
</div>
<div class="ulist checklist">
@@ -425,13 +425,9 @@ This is the version the <code>develop</code> branch will be changed to.</p>
<p>In contrast to normal builds, it is important to enable all profiles when creating the branch as only this way will all modules versions be updated.
Otherwise the non-default modules on develop will reference the old version which will cause problems when building.</p>
</div>
-<div class="paragraph">
-<p>The parameter <code>autoVersionSubmodules</code> will tell the release plugin to release all modules with the same version.
-Otherwise we would have to define the working copy version for each module.</p>
-</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:branch -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DbranchName=rel/{minor-version} -DautoVersionSubmodules=true</pre>
+<pre>mvn release:branch -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DbranchName=rel/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -440,7 +436,7 @@ So in case of preparing the release branch for <code>0.7.0-SNAPSHOT</code> the c
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DbranchName=rel/0.7 -DautoVersionSubmodules=true</pre>
+<pre> mvn release:branch -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DbranchName=rel/0.7</pre>
</div>
</div>
<div class="paragraph">
@@ -532,7 +528,7 @@ In order to prepare a release-candidate, the first step is switching to the corr
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:prepare -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash -DautoVersionSubmodules=true</pre>
+<pre>mvn release:prepare -P with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash</pre>
</div>
</div>
<div class="paragraph">