triz-docs/docs/getting-started/environment-setup/05-ide-configuration.md

sidebar_position	title
6	IDE Configuration

IDE Configuration

---

Step 10 — Install and Configure NetBeans 17

10.1 — Install NetBeans

1. Download NetBeans 17 from:
   • Gitea release assets
   • Apache
2. Run the installer and complete the installation with default settings.

10.2 — Register JDK 8

NetBeans may detect a newer JDK if you have one installed. Ensure it is using JDK 8 for this project.

1. Open NetBeans → Tools → Java Platforms.
2. Check that JDK 1.8 is listed. If not, click Add Platform, select Java Standard Edition, and navigate to your JDK 8 installation directory (your JAVA_HOME path).
3. Click Finish, then Close.

10.3 — Register Tomcat 9

1. Go to Tools → Servers → Add Server.
2. Select Apache Tomcat or TomEE and click Next.
3. Set the Server Location to your Tomcat 9 directory (e.g., C:\dev\tomcat9).
4. Set a username and password for the Tomcat manager (you can use any values for local development, e.g., admin / admin).
5. Click Finish.

10.4 — Configure Maven in NetBeans

1. Go to Tools → Options → Java → Maven.
2. Under Maven Home, click Browse and point it to your Maven installation directory (C:\dev\maven). Do not use the "Bundled" option.
3. Click OK.

10.5 — Open the Project

1. Go to File → Open Project.
2. Navigate to your cloned stock folder and select it. NetBeans will recognize it as a Maven project.
3. Click Open Project.

---

Step 11 — Build and Verify

This final step confirms that your entire environment is wired up correctly.

11.1 — Build the Project

1. In NetBeans, right-click the Stock project in the Projects panel.
2. Select Clean and Build.
3. Monitor the Output panel at the bottom. The build must end with:

BUILD SUCCESS

If you see BUILD FAILURE with dependency errors, revisit Step 3 (Maven settings.xml and Gitea registry).

11.2 — Deploy and Run

1. Right-click the project → Run.
2. NetBeans will deploy the application to your local Tomcat 9 instance and open it in the browser.
3. The application should load without any database connection errors.

11.3 — Verify Database Connectivity

1. Log in to the application using the test credentials (ask your team lead for the default test user).
2. Navigate to any section that loads data from the database (e.g., the stock listing page).
3. If data loads correctly, your environment is fully operational.