CCS Workstation Provisioning: Java 26, Spring Tools 5 & Gradle Baseline

Open the system terminal and execute the global apt repository update sequence along with core utility registration to verify Git, Curl, Unzip, and standard compilation tools are present:

sudo apt update && sudo apt upgrade -y && sudo apt install git curl build-essential wget unzip -y

Initialize the SDKMAN! runtime management engine directly from its verified installation mirror to bypass local environmental path tracking issues:

curl -s "https://get.sdkman.io" | bash

Provision the Java compilation platform engine via SDKMAN! and register it as your explicit system-wide default sandbox environment:

sdk install java 26-open

Pull down the upgraded Spring Tools 5 standalone Linux archive package from the official Spring release matrix and extract its payload into an isolated tooling folder:

mkdir -p ~/tools && cd ~/tools && wget https://cdn.spring.io/spring-tools/release/dist/5.1.1.RELEASE/e4.39/spring-tools-for-eclipse-5.1.1.RELEASE-e4.39.0-linux.gtk.x86_64.tar.gz && tar -xvf spring-tools-for-eclipse-5.1.1.RELEASE-e4.39.0-linux.gtk.x86_64.tar.gz

Register the application launcher profile directly within your native Linux Mint Cinnamon or MATE desktop environments catalog by crafting a custom desktop application profile descriptor file inside your local application directory paths:

nano ~/.local/share/applications/sts5.desktop

Launch an administrative Windows Terminal instance or elevated PowerShell session. Bypass native Windows App Store repository certification failures by instructing winget to explicitly tap the community repository layout directly to provision Git:

winget install Git.Git -e --source winget

Deploy the exact production-ready BellSoft Liberica OpenJDK compilation binary suite matching your active development architecture natively via winget execution rules:

winget install BellSoft.LibericaJDK.26 -e --source winget

Pull down the raw Spring Tools 5 zip distribution payload and extract its structure components directly into a root-level system folder directory:

New-Item -ItemType Directory -Force -Path "C:\tools\sts5"; cd C:\tools\sts5; Invoke-WebRequest -Uri "https://cdn.spring.io/spring-tools/release/dist/5.1.1.RELEASE/e4.39/spring-tools-for-eclipse-5.1.1.RELEASE-e4.39.0-win32.win32.x86_64.zip" -OutFile "sts5.zip"; Expand-Archive -Path "sts5.zip" -DestinationPath "C:\tools\sts5"

Navigate straight within your newly unpacked deployment workspace directory path located specifically at:
C:\tools\sts5\sts-5.1.1.RELEASE\
Right-click the file named SpringToolsForEclipse.exe, create a system shortcut, and select Pin to Start or Pin to Taskbar to fully replace legacy dead links.

Deploy the official GitHub CLI tool straight onto your operating environment platform interface to eliminate manual SSH credential tracking issues completely. For Mint:

sudo apt install gh -y

winget install GitHub.cli -e --source winget

Trigger the interactive browser validation handshake protocol right inside your open terminal framework workspace:

gh auth login

Set up the destination landing path folders for your local websites stack, navigate inside them, and download the active repository codebase using your newly authenticated shell session:

gh repo clone dac5190/CatinoComputerSolutions_Java

Launch your IDE tool suite application and map your workspace framework anchor base to a dedicated directory layout space, such as:
C:\eclipse-workspace
Navigate to Window, select Preferences, drop open Java, and click on Installed JREs.

Click Add..., select Standard VM, and hit Next. Click the Directory... browser button to target the path of your active Liberica JDK environment directory installation:
C:\Program Files\BellSoft\LibericaJDK-26 or /home/dav/.sdkman/candidates/java/26-open
Name the profile 'LibericaJDK-26', click Finish, and check its checkbox to assert it as the workspace default.

Expand the Installed JREs node on the left list, select Execution Environments, highlight JavaSE-26 in the center pane, and check the checkbox right beside LibericaJDK-26 in the right-hand compatibility mapping matrix column.

Switch your preferences tab over into the Gradle configurations view segment. Locate the Advanced Options container section block, find the input field named 'Java home', and completely delete any values hidden inside it to wipe it entirely blank.

Directly below the cleared parameter box, switch the 'Gradle JVM' dropdown element parameter choice to explicitly register to 'Workspace JVM (LibericaJDK-26)'. Click Apply and Close.

Import your source code into the active IDE instance by clicking File, selecting Import..., dropping open Gradle, and choosing Existing Gradle Project. Target your local CatinoComputerSolutions_Java path folder layout and click Finish.

Right-click your website project root ccs inside the Package Explorer navigation stack tree, open Properties, select Java Build Path, and click into the Order and Export layout panel sheet tab.

Right-click your primary website project node folder layout container, click Gradle, and execute a Refresh Gradle Project command sequence to re-index the build script models completely.

Flush old build artifact compiler cache files by clicking Project on the top software menu bar, selecting Clean..., checking 'Clean all projects', and clicking the confirmation Clean trigger button.