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 659b6d1 Site checkin for project PLC4X: Jenkins Tools
659b6d1 is described below
commit 659b6d15b1f00a71d0d5755f77b421b84b120e7c
Author: jenkins <[email protected]>
AuthorDate: Fri Sep 10 11:03:52 2021 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/release/release.html | 14 +++++++-------
developers/release/validation.html | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/developers/release/release.html b/developers/release/release.html
index 1906f7c..4dae04e 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -255,7 +255,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-c,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{current-short-version}</pre>
+<pre> mvn release:branch -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -270,7 +270,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-c,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre> mvn release:prepare -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox</pre>
</div>
</div>
<div class="ulist checklist">
@@ -471,7 +471,7 @@ Otherwise, the non-default modules on develop will
reference the old version whi
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:branch -P with-c,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{minor-version}</pre>
+<pre>mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -480,7 +480,7 @@ So in case of preparing the release branch for
<code>0.9.0-SNAPSHOT</code> the c
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox -DbranchName=rel/0.9</pre>
+<pre> mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/0.9</pre>
</div>
</div>
<div class="paragraph">
@@ -572,11 +572,11 @@ 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-c,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre>mvn release:prepare -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox</pre>
</div>
</div>
<div class="paragraph">
-<p>(The <code>-P with-c,with-dotnet,with-go,with-python,with-sandbox</code>
tells maven to activate the all profiles that partition the build and makes
sure the versions of all modules are updated as part of the release)
+<p>(The <code>-P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox</code>
tells maven to activate the all profiles that partition the build and makes
sure the versions of all modules are updated as part of the release)
In general the plugin will now ask you 3 questions:</p>
</div>
<div class="olist arabic">
@@ -705,7 +705,7 @@ If the commit history doesn’t look like this,
something went wrong.
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:perform</pre>
+<pre>mvn release:perform -DreleaseProfiles=apache-release</pre>
</div>
</div>
<div class="paragraph">
diff --git a/developers/release/validation.html
b/developers/release/validation.html
index 7330f8c..039bcef 100644
--- a/developers/release/validation.html
+++ b/developers/release/validation.html
@@ -386,7 +386,7 @@ Especially in the <code>sandbox</code> there may be parts
that are not formally
<div class="sect2">
<h3 id="release_tooling">Release Tooling</h3>
<div class="paragraph">
-<p>In the <code>tools</code> directory we have a little script that can help
with downloading and checking the hashes and signatures automatically.</p>
+<p>In the <code>tools</code> directory we have a little script that can help
downloading and checking the hashes and signatures automatically.</p>
</div>
<div class="paragraph">
<p>In order to execute this, please change directories into the projects base
directory and execute the following command:</p>
