فهم بنية مشروع Spring Boot

Spring Initializr hands you a ready-to-run skeleton: a build file, a main class, a properties file, and a test class. Knowing each part lets you navigate with confidence.

The build file — pom.xml for Maven, build.gradle for Gradle — declares your dependencies, Java version, and the Spring Boot plugin that packages the app.

A starter is a curated bundle of libraries. spring-boot-starter-web pulls in everything for a web app, so you never juggle individual versions.

The main class is your entry point: annotated with @SpringBootApplication and holding a standard Java main method that boots the framework.

Stick to the convention: code in src/main/java, config and assets in src/main/resources, and tests under src/test. Spring Boot finds it all automatically.

The resources folder holds application.properties (or .yml) for config, static/ for assets, and templates/ for views.

Spring Boot scans from your main class's package downward. Keep controllers and services in sub-packages of that root so they're discovered automatically.

The wrapper scripts (mvnw, gradlew) let anyone build the project without installing Maven or Gradle, locking in a consistent tool version.

Initializr adds a context-load test with @SpringBootTest. If the application context starts cleanly, the test passes — proving your wiring is valid.

Building outputs to target/ (Maven) or build/ (Gradle), including a runnable fat JAR that bundles your code plus an embedded server.

You can run the app three ways: from your IDE, via the wrapper, or by executing the packaged JAR. All three start the embedded server.

You toured the build file, starters, main class, resources, source layout, wrappers, and artifacts. Knowing this structure makes the rest of Spring Boot click.