Installing Tools

This chapter walks you through installing the prerequisite tools for each OS. Each tool section includes a verification step, so always confirm success with the version check command before moving on.

Windows

Windows

Bun

Installation steps:

1. Open PowerShell (see Opening a Terminal).

2. Run the following command (the official Windows installer):

   powershell -c "irm bun.sh/install.ps1|iex"

3. After installation, close and reopen the terminal (to apply the PATH update).

For the latest details, refer to the official site: https://bun.com/docs/installation#windows

If blocked by PowerShell execution policy

If you see an error such as Running scripts is disabled on this system…, run the following command to allow execution for the current user only, then retry:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

Verification:

bun --version

Expected output (example):

1.3.14

Confirm the displayed version is 1.3.14 or later.

Java (JDK)

Selection policy: Choose a JDK supported by iAP. Always check the release notes for your target iAP version in the intra-mart Accel Series document archive. This guide assumes JDK 8 or JDK 11 as listed in the release notes.

Installation steps (Oracle JDK example):

1. Go to the appropriate download page:
   • JDK 8: https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html
   • JDK 11: https://www.oracle.com/java/technologies/javase/jdk11-archive-downloads.html
2. Download the Windows x64 Installer.
3. Run the downloaded installer and follow the wizard to complete installation.
4. Note the installation folder (e.g., C:\Program Files\Java\jdk-11.x.x).

Setting environment variables:

On Windows, you need to set JAVA_HOME and PATH.

1. Open the "Environment Variables" dialog:
   • Type "environment variables" in the Start menu → select "Edit the system environment variables" → click the "Environment Variables" button.
2. Under "System variables", add a new variable JAVA_HOME with the installation folder as its value.
3. Edit the Path system variable and append %JAVA_HOME%\bin.
4. Click OK to close, then close and reopen the terminal.

If multiple Java versions are installed

If a previously installed Java version remains, java -version may display an unintended version. In that case, set JAVA_HOME to the desired version and temporarily remove any existing Java references from Path (e.g., C:\Program Files\Common Files\Oracle\Java\javapath).

Verification:

java -version

Expected output (example):

java version "11.0.29" 2025-10-21 LTS
Java(TM) SE Runtime Environment ...
Java HotSpot(TM) 64-Bit Server VM ...

Confirm the displayed version is 1.8.x or 11.x.

Maven

Installation steps:

1. Download the Binary zip archive (e.g., apache-maven-3.9.14-bin.zip) from https://maven.apache.org/download.cgi.
2. Extract it to a folder of your choice (e.g., C:\tools\apache-maven-3.9.14).
3. Set environment variables (in the same dialog as Java (JDK)):
   • Add MAVEN_HOME as a new variable with the extracted folder as its value.
   • Append %MAVEN_HOME%\bin to Path.
4. Close and reopen the terminal.

For more details, refer to the official site: https://maven.apache.org/install.html

Verification:

mvn --version

Expected output (example):

Apache Maven 3.9.14 (...)
Maven home: C:\tools\apache-maven-3.9.14
Java version: 11.0.29, vendor: ...

Confirm the displayed version is 3.9.14 or later.

Visual Studio Code

Installation steps:

1. Download the Windows installer from https://code.visualstudio.com/.
2. Run the installer. On the "Select Additional Tasks" screen, it is recommended to check the following options:
   • "Add to PATH" (enables the code command)
   • "Add 'Open with Code' action to Windows Explorer context menu" (enables opening folders by right-clicking)
3. After installation, close and reopen the terminal.

For more details, refer to the official site: https://code.visualstudio.com/docs/setup/windows

Verification:

code --version

Expected output (example):

1.127.0
xxxxxxxxxxxxxxx
x64

Confirm the displayed version is 1.127.0 or later.

Git

If you are not using version control

If you do not plan to use Git for version control, installation is not required. If you plan to manage your project remotely on GitHub or similar, prepare an account for the corresponding service separately.

Installation steps:

1. Download the Windows installer from https://git-scm.com/download/win.

2. Run the installer. It is generally fine to proceed with the default settings.

3. After installation, close and reopen the terminal.

4. As initial setup, configure your username and email address (this information is used in commit signatures):

   git config --global user.name "Your Name"
   git config --global user.email "you@example.com"

For more details, refer to the official site: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git

Verification:

git --version

Expected output (example):

git version 2.53.0.windows.3

Confirm the displayed version is 2.53.0 or later.

macOS

macOS

Bun

Installation steps:

1. Open Terminal.app (see Opening a Terminal).

2. Run the following command:

   curl -fsSL https://bun.com/install | bash

3. After installation, reload ~/.zshrc as instructed, or close and reopen the terminal.

For more details, refer to the official site: https://bun.com/docs/installation#macos-linux

Verification:

bun --version

Expected output (example):

1.3.14

Confirm the displayed version is 1.3.14 or later.

Java (JDK)

Selection policy: Choose a JDK supported by iAP. Always check the release notes for your target iAP version in the intra-mart Accel Series document archive. This guide assumes JDK 8 or JDK 11 as listed in the release notes.

Installation steps (Oracle JDK example):

1. Go to the appropriate download page:
   • JDK 8: https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html
   • JDK 11: https://www.oracle.com/java/technologies/javase/jdk11-archive-downloads.html
2. Download the DMG file (.dmg).
3. Open the downloaded DMG file and follow the wizard to complete installation.

Installation steps (Homebrew example):

brew install --cask corretto@11

Setting JAVA_HOME:

Add the following to ~/.zshrc (for zsh) or ~/.bash_profile (for bash), according to your shell:

• JDK 8 example:

export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
export PATH="$JAVA_HOME/bin:$PATH"

• JDK 11 example:

export JAVA_HOME=$(/usr/libexec/java_home -v 11)
export PATH="$JAVA_HOME/bin:$PATH"

After editing, run source ~/.zshrc to apply the changes, or close and reopen the terminal.

Verification:

java -version

Expected output (example):

java version "11.0.29" 2025-10-21 LTS
Java(TM) SE Runtime Environment ...
Java HotSpot(TM) 64-Bit Server VM ...

Confirm the displayed version is 1.8.x or 11.x.

Maven

Installing via Homebrew is the easiest option.

brew install maven

For more details, refer to the official site: https://maven.apache.org/install.html

Verification:

mvn --version

Expected output (example):

Apache Maven 3.9.14 (...)
Maven home: /opt/homebrew/Cellar/maven/3.9.14/libexec
Java version: 11.0.29, vendor: ...

Confirm the displayed version is 3.9.14 or later.

Visual Studio Code

Installation steps:

1. Download the DMG file (.dmg) from https://code.visualstudio.com/.
2. Open the downloaded DMG file and drag Visual Studio Code.app to the "Applications" folder.
3. Double-click VSCode in the "Applications" folder to launch it.
4. Open the Command Palette (Shift + Command + P) and run Shell Command: Install 'code' command in PATH to enable the code command in the terminal.

For more details, refer to the official site: https://code.visualstudio.com/docs/setup/mac

Verification:

code --version

Expected output (example):

1.127.0
xxxxxxxxxxxxxxx
x64

Confirm the displayed version is 1.127.0 or later.

Git

If you are not using version control

If you do not plan to use Git for version control, installation is not required. If you plan to manage your project remotely on GitHub or similar, prepare an account for the corresponding service separately.

macOS includes Git via Xcode Command Line Tools, but the bundled version may be outdated. This guide requires 2.53.0 or later, so installation via Homebrew is recommended.

brew install git

If not using Homebrew

The Xcode Command Line Tools version can be installed with xcode-select --install. However, if the bundled version is below 2.53.0, install the Homebrew version instead.

Initial setup:

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

For more details, refer to the official site: https://git-scm.com/install/mac

Verification:

git --version

Expected output (example):

git version 2.53.0

Confirm the displayed version is 2.53.0 or later.

Linux

Linux

The examples below use Debian/Ubuntu (apt) and RHEL/Fedora (dnf). Adapt the commands to your distribution as needed.

Bun

1. Open a terminal (see Opening a Terminal).

2. Run the following command:

   curl -fsSL https://bun.com/install | bash

3. After installation, close and reopen the terminal.

For more details, refer to the official site: https://bun.com/docs/installation#macos-linux

Verification:

bun --version

Expected output (example):

1.3.14

Confirm the displayed version is 1.3.14 or later.

Java (JDK)

Selection policy: Choose a JDK supported by iAP. Always check the release notes for your target iAP version in the intra-mart Accel Series document archive. This guide assumes JDK 8 or JDK 11 as listed in the release notes.

Oracle JDK packages for Linux vary in format depending on the JDK version.

JDK version	.tar.gz	.rpm (RHEL / Fedora / CentOS)	.deb (Debian / Ubuntu)
JDK 8	○	○	× (not available)
JDK 11	○	○	○

For JDK 11, using a package file (.deb / .rpm) matching your distribution is the simplest approach. For JDK 8, or if a matching package is not available for your distribution, extract the .tar.gz manually.

Download from the following pages:

• JDK 8: https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html
• JDK 11: https://www.oracle.com/java/technologies/javase/jdk11-archive-downloads.html

Installing JDK 11

Debian / Ubuntu example (using .deb):

1. Download the .deb package (e.g., jdk-11.x.xx_linux-x64_bin.deb) from the JDK 11 download page above.

2. In the directory where you downloaded the file, run the following command. The installation path will be /usr/lib/jvm/jdk-11.x.xx-oracle-x64.

   sudo dpkg -i ./<downloaded-filename>.deb

RHEL / Fedora / CentOS example (using .rpm):

1. Download the .rpm package (e.g., jdk-11.x.xx_linux-x64_bin.rpm) from the JDK 11 download page above.

2. In the directory where you downloaded the file, run the following command. The installation path will be /usr/lib/jvm/jdk-11.x.xx-oracle-x64 (where 11.x.xx is your downloaded version). For RPM installs, a backward-compatibility symlink /usr/java/jdk-11 is also created.

   sudo rpm -ivh ./<downloaded-filename>.rpm

Installing from an archive (.tar.gz)

1. Download the .tar.gz from the download page above.

2. Create a directory for Java (e.g., /usr/lib/jvm):

   sudo mkdir -p /usr/lib/jvm

3. In the directory where you downloaded the file, run the following command to extract it to the created directory:

   sudo tar zxvf ./<downloaded-filename>.tar.gz -C /usr/lib/jvm

Setting JAVA_HOME (all installation methods)

Open ~/.bashrc in a text editor and append the following (replace the path with your actual installation or extraction path):

# Example for .deb / .rpm installation (JDK 11):
export JAVA_HOME=/usr/lib/jvm/jdk-11.x.xx-oracle-x64
export PATH="$JAVA_HOME/bin:$PATH"

# Example for .tar.gz extraction:
export JAVA_HOME=/usr/lib/jvm/<extracted-directory-name>
export PATH="$JAVA_HOME/bin:$PATH"

After editing, run the following command or close and reopen the terminal to apply the changes:

source ~/.bashrc

Verification:

java -version

Expected output (example):

java version "11.0.29" 2025-10-21 LTS
Java(TM) SE Runtime Environment ...
Java HotSpot(TM) 64-Bit Server VM ...

Confirm the displayed version is 1.8.x or 11.x.

Maven

Debian / Ubuntu example:

sudo apt install -y maven

RHEL / Fedora example:

sudo dnf install -y maven

If the Maven version provided by your distribution is lower than 3.9.14, download the archive from the official site https://maven.apache.org/download.cgi and install manually.

Installing from an archive (.tar.gz) example:

1. Download the archive (.tar.gz) from https://maven.apache.org/download.cgi.

2. In the directory where you downloaded the file, run the following command to extract it to a directory of your choice (e.g., /opt):

   sudo tar zxvf ./<downloaded-filename>.tar.gz -C /opt

3. Open ~/.bashrc in a text editor and append the following:

   export PATH="/opt/<extracted-directory-name>/bin:$PATH"

4. After editing, run the following command or close and reopen the terminal to apply the changes:

   source ~/.bashrc

Verification:

mvn --version

Expected output (example):

Apache Maven 3.9.14
Maven home: /usr/share/maven
Java version: 11.0.29, vendor: ...

Confirm the displayed version is 3.9.14 or later.

Visual Studio Code

Distribution-specific instructions are available at https://code.visualstudio.com/docs/setup/linux. This guide describes the simplest approach: installing directly from a package file.

Debian / Ubuntu example (direct .deb install):

1. Download the .deb package from https://code.visualstudio.com/.

2. In the directory where you downloaded the file, run:

   sudo apt install ./<downloaded-filename>.deb

RHEL / Fedora / CentOS example (direct .rpm install):

1. Download the .rpm package from https://code.visualstudio.com/.

2. In the directory where you downloaded the file, run:

   sudo dnf install ./<downloaded-filename>.rpm

For automatic updates (adding APT / DNF repository)

To keep VSCode up to date alongside system updates, add Microsoft's package repository. Refer to the "Install VS Code on Debian and Ubuntu based distributions" or "RHEL, Fedora, and CentOS based distributions" sections at https://code.visualstudio.com/docs/setup/linux.

Verification:

code --version

Expected output (example):

1.127.0
xxxxxxxxxxxxxxx
x64

Confirm the displayed version is 1.127.0 or later.

Git

If you are not using version control

If you do not plan to use Git for version control, installation is not required. If you plan to manage your project remotely on GitHub or similar, prepare an account for the corresponding service separately.

Debian / Ubuntu example:

sudo apt install -y git

If the apt package on Ubuntu is outdated

If the version of Git provided by Ubuntu's standard repository is below 2.53.0, add the official PPA maintained by the Git maintainers (ppa:git-core/ppa) and install the latest version:

sudo add-apt-repository ppa:git-core/ppa
sudo apt update
sudo apt install -y git

RHEL / Fedora example:

sudo dnf install -y git

If the dnf package is outdated

If the standard repository version is below 2.53.0, the official site provides instructions for building from source. Refer to https://git-scm.com/install/linux.

Initial setup:

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

For more details, refer to the official site: https://git-scm.com/install/linux

Verification:

git --version

Expected output (example):

git version 2.53.0

Confirm the displayed version is 2.53.0 or later.

Environment Variable Settings

Here is a summary of the key points about the environment variables you set in the OS-specific steps. Register the Java SE Development Kit and Apache Maven as environment variables.

• JAVA_HOME: The folder where you installed the Java SE Development Kit
• MAVEN_HOME: The folder where you installed Apache Maven

Also, add each of their bin folders to the PATH environment variable.

• On Linux / macOS
  • PATH=$JAVA_HOME/bin:$MAVEN_HOME/bin:$PATH
• On Windows
  • PATH=%JAVA_HOME%\bin;%MAVEN_HOME%\bin;%PATH%

The Maven settings file is generated automatically

The Maven settings file (settings.xml) and the reference settings for intra-mart's Maven repository are generated automatically under the project when you create a project with Accel CLI. Therefore, you do not need to manually configure settings under your home directory (such as ~/.m2/settings.xml).

If a problem occurs during the setup steps

Refer to Troubleshooting.