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 afb9e7d0d Site checkin for project PLC4X: Jenkins Tools
afb9e7d0d is described below
commit afb9e7d0d586b30920a9a5d1d6b283902adca01b
Author: jenkins <[email protected]>
AuthorDate: Tue Feb 6 15:23:16 2024 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/building.html | 7 +++++--
developers/release/release.html | 16 ++++++++--------
modules.html | 5 +----
3 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/developers/building.html b/developers/building.html
index 1eebac79d..3b4238687 100644
--- a/developers/building.html
+++ b/developers/building.html
@@ -335,6 +335,9 @@ But there is a lot of good documentation out there.</p>
<p><code>with-go</code>: Builds all Go related modules, integrations and
examples</p>
</li>
<li>
+<p><code>with-java</code>: Builds all Java related modules, integrations and
examples</p>
+</li>
+<li>
<p><code>with-python</code>: Builds all Python related modules, integrations
and examples (Also requires <code>with-sandbox</code>)</p>
</li>
<li>
@@ -404,7 +407,7 @@ Currently when enabling the <code>with-python</code>
module, you are required to
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn -P with-c,with-dotnet,with-go,with-python,with-sandbox install</pre>
+<pre>mvn -P with-c,with-dotnet,with-go,with-java,with-python,with-sandbox
install</pre>
</div>
</div>
<div class="paragraph">
@@ -415,7 +418,7 @@ Currently when enabling the <code>with-python</code>
module, you are required to
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn -P with-c,with-dotnet,with-go,with-python,with-sandbox install
-DskipTests</pre>
+<pre>mvn -P with-c,with-dotnet,with-go,with-java,with-python,with-sandbox
install -DskipTests</pre>
</div>
</div>
<div class="paragraph">
diff --git a/developers/release/release.html b/developers/release/release.html
index 8caedd23d..ad8d8dfa8 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -272,7 +272,7 @@ Please be sure to execute the release with a Java version
11 or the Karaf featur
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks
-DbranchName=rel/{current-short-version}</pre>
+<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks
-DbranchName=rel/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -287,7 +287,7 @@ Please be sure to execute the release with a Java version
11 or the Karaf featur
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:prepare -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
+<pre> mvn release:prepare -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
<div class="ulist checklist">
@@ -503,7 +503,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,enable-all-checks
-DbranchName=rel/{minor-version}</pre>
+<pre>mvn release:branch -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks
-DbranchName=rel/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -512,7 +512,7 @@ So in case of preparing the release branch for
<code>0.12.0-SNAPSHOT</code> the
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks
-DbranchName=rel/0.12</pre>
+<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks
-DbranchName=rel/0.12</pre>
</div>
</div>
<div class="paragraph">
@@ -604,11 +604,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,enable-all-checks</pre>
+<pre>mvn release:prepare -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
<div class="paragraph">
-<p>(The <code>-P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</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-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks</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">
@@ -721,7 +721,7 @@ If the commit history doesn’t look like this,
something went wrong.
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:rollback -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
+<pre>mvn release:rollback -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
<div class="paragraph">
@@ -970,7 +970,7 @@ This is done by moving them inside the Apache SVN.</p>
<p>Set the versions of the release branch to the previous version by using the
<code>versions:set</code> plugin:</p>
<div class="literalblock">
<div class="content">
-<pre>mvn versions:set -DprocessAllModules=true -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
+<pre>mvn versions:set -DprocessAllModules=true -P
with-c,with-dotnet,with-go,with-java,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
</li>
diff --git a/modules.html b/modules.html
index 836ae2daf..36aa13983 100644
--- a/modules.html
+++ b/modules.html
@@ -132,10 +132,7 @@
<th>Description</th></tr>
<tr class="b">
<td align="left"><a href="./plc4x-protocols/index.html">Protocols</a></td>
-<td>Base protocol specifications.</td></tr>
-<tr class="a">
-<td align="left"><a href="./plc4j/index.html">PLC4J</a></td>
-<td>Implementation of the protocol adapters for usage as Java
library.</td></tr></table></section>
+<td>Base protocol specifications.</td></tr></table></section>
</main>
<footer class="pt-4 my-md-5 pt-md-5 w-100 border-top">
<div class="row justify-content-md-center" style="font-size: 13px">
