This is an automated email from the ASF dual-hosted git repository.
Kusuma04-dev pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kie-website.git
The following commit(s) were added to refs/heads/main by this push:
new 20677eda [incubator-kie-website] [NO-ISSUE]: Updated build procedure
for 10.3 (#97)
20677eda is described below
commit 20677eda9c2a596e98fdd71ea0de0ef85d3aa0a0
Author: Kusuma04-dev <[email protected]>
AuthorDate: Fri Nov 20 11:52:28 2026 +0530
[incubator-kie-website] [NO-ISSUE]: Updated build procedure for 10.3 (#97)
* updated build doc
---------
Co-authored-by: kusuma-latha <[email protected]>
---
docs/community/devs/build-10.3.0.md | 65 ++++++++++++++++++++++---------------
docs/community/devs/verify.md | 2 +-
2 files changed, 39 insertions(+), 28 deletions(-)
diff --git a/docs/community/devs/build-10.3.0.md
b/docs/community/devs/build-10.3.0.md
index 5b08d843..ce80af1f 100644
--- a/docs/community/devs/build-10.3.0.md
+++ b/docs/community/devs/build-10.3.0.md
@@ -38,48 +38,66 @@ If using rancher:
export DOCKER_HOST=unix://$HOME/.rd/docker.sock
```
-If using podman:
-
- ```bash
- export DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock
- ```
+:::
+:::NOTE
+Podman is not supported for building. Use Docker (or a Docker-API compatible
engine such as colima or Rancher Desktop).
:::
### 1. Obtain the source code
-Release candidates are published in the Apache dev SVN, one folder per RC:
+The first step in building from source is to obtain and extract the source
code archive. Since 10.3.0 a single archive contains the source code of both
repositories (`incubator-kie` and `incubator-kie-tools`).
+#### Download the source archive
+
+Release candidates are published in the Apache dev SVN, one folder per RC. Use
the following pattern to locate and download the source zip:
+
+```bash
+https://dist.apache.org/repos/dist/dev/incubator/kie/10.3.0-${rc_version}/apache-kie-10.3.0-incubating-sources.zip
```
-https://dist.apache.org/repos/dist/dev/incubator/kie/10.3.0-${rc_version}/
+
+Replace `${rc_version}` with the appropriate value. For example:
+
+```bash
+https://dist.apache.org/repos/dist/dev/incubator/kie/10.3.0-rc1/apache-kie-10.3.0-incubating-sources.zip
```
-The SVN folder contains only the Tools source archive (`incubator-kie-tools`).
Download it (replace `rc1` with the RC you want to build):
+:::tip
+Before building, verify signatures and checksums as described in [How to
verify a release candidate](/community/devs/verify).
+:::
+
+#### Extract the source archive
+
+Once downloaded, extract the contents of the zip file:
```bash
-BASE=https://dist.apache.org/repos/dist/dev/incubator/kie/10.3.0-rc1
-curl -O $BASE/apache-kie-10.3.0-incubating-sources.zip # Tools
(incubator-kie-tools)
unzip apache-kie-10.3.0-incubating-sources.zip
```
-The Java code (`incubator-kie`) is not published as a source archive. Check
out the RC tag instead:
+### 2. Navigate to the source directory
```bash
-git clone --branch 10.3.0-rc1 --depth 1
https://github.com/apache/incubator-kie.git
+cd apache-kie-10.3.0-incubating
```
+The directory contains:
-:::tip
-Before building, verify signatures and checksums as described in [How to
verify a release candidate](/community/devs/verify).
-:::
+- BUILD
+- DISCLAIMER-WIP
+- LICENSE
+- NOTICE
+- incubator-kie
+- incubator-kie-tools
+
+The `BUILD` file has short build instructions and the tool versions for this
release. We'll build the two repositories individually: first `incubator-kie`,
then `incubator-kie-tools`, which resolves the Java artifacts from the local
Maven repository.
-### 2. Build
+### 3. Building individual components
:::note
It's recommended to clean the local `~/.m2` repository first, because its
content is incorporated in some container images during the build.
:::
-### 2.1. Java (Drools, Kogito, OptaPlanner, apps)
+### 3.1. Java (Drools, Kogito, OptaPlanner, apps) - `incubator-kie`
**Environment requirements:** Temurin JDK, Maven, Docker.
@@ -87,25 +105,18 @@ It's recommended to clean the local `~/.m2` repository
first, because its conten
```bash
cd incubator-kie
mvn clean install -DskipTests -Dfull
+cd ..
```
-:::note
-If you're using Podman as the Docker API, also pass:
-
- ```bash
- -Djib.dockerClient.executable=$(which podman)
- ```
-:::
-
**Produced artifacts:** JARs are installed to the local Maven repository.
-### 2.2. KIE Tools
+### 3.2. KIE Tools - `incubator-kie-tools`
**Environment requirements:** Temurin JDK, Maven, Node, PNPM, Go, Python,
Helm, Docker, Make.
**Build commands:**
```bash
-cd apache-kie-10.3.0-incubating
+cd incubator-kie-tools
git init .
git config user.name "Your Name"
git config user.email "[email protected]"
diff --git a/docs/community/devs/verify.md b/docs/community/devs/verify.md
index 5e36331e..d0cc18d7 100644
--- a/docs/community/devs/verify.md
+++ b/docs/community/devs/verify.md
@@ -149,7 +149,7 @@ Open a `.drl` file and check that syntax highlighting and
code completion work.
## Check the file content of the source package
-The SVN dev folder contains one source archive,
`apache-kie-${release_version}-incubating-sources.zip` (Tools,
`incubator-kie-tools`). The Java code (`incubator-kie`) is released through the
Nexus staging repository (JARs, POMs, sources and Javadocs), not as a source
ZIP in SVN.
+The SVN dev folder contains one source archive,
`apache-kie-${release_version}-incubating-sources.zip`, with the source code of
both repositories. Its root directory contains `BUILD`, `DISCLAIMER-WIP`,
`LICENSE`, `NOTICE`, `incubator-kie` and `incubator-kie-tools`. The Java
artifacts (JARs, POMs, sources and Javadocs) are additionally released through
the Nexus staging repository.
Unzip the archive and check the following:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]