How to Run Your First Spring Boot Application in IntelliJ?
Feb 07, 2025 am 11:40 AMIntelliJ IDEA simplifies Spring Boot development, making it a favorite among Java developers. Its convention-over-configuration approach minimizes boilerplate code, allowing developers to focus on business logic. This tutorial demonstrates two methods for creating and running a basic Spring Boot application within IntelliJ IDEA.
This powerful IDE facilitates project creation with necessary dependencies and importing existing Spring Boot projects. Before beginning, ensure you have:
- A Java Development Kit (JDK) installed.
- IntelliJ IDEA installed and configured.
- Basic understanding of Java and Spring concepts.
Setting Up Your Spring Boot Project in IntelliJ IDEA
Step 1: IntelliJ IDEA Installation
- Visit the IntelliJ IDEA website: http://www.miracleart.cn/link/e8cb5f581442030021d62fd780fa674d
- Click the "Download" button.
- Select your preferred edition (Community or Ultimate).
- Download and install, following on-screen instructions.
- Launch IntelliJ IDEA and complete the initial setup.
Step 2: Project Generation using Spring Initializr
- Navigate to the Spring Initializr website: http://www.miracleart.cn/link/bafd1b75c5f0ceb81050a853c9faa911
- Specify project details:
- Select your Spring Boot version.
- Enter a Group name.
- Enter an Artifact name (e.g.,
newProject
). - Choose required dependencies (e.g., Spring Web).
- Click "Generate" to download the project as a ZIP file.
Step 3: Creating and Configuring the Spring Boot Project
There are two approaches: using Spring Initializr or creating a Maven project directly in IntelliJ.
Approach 1: Using Spring Initializr
- Open the downloaded ZIP file in IntelliJ IDEA.
- Create a
controller
package undernewProject -> src/main/java
. - Create a class
ExampleC
within thecontroller
package.
- Add the following code to
ExampleC
, ensuring you import necessary annotations:
package org.example.controller; import org.springframework.web.bind.annotation.RequestMapping; import org.springframework.stereotype.Controller; import org.springframework.web.bind.annotation.ResponseBody; @Controller public class ExampleC { @RequestMapping("/firstApp") @ResponseBody public String firstSpringApp(){ return "Welcome!"; } }
Approach 2: Creating a Maven Project in IntelliJ
- Create a new Maven project in IntelliJ.
- Add the following dependencies to your
pom.xml
within the<dependencies>
tag:
package org.example.controller; import org.springframework.web.bind.annotation.RequestMapping; import org.springframework.stereotype.Controller; import org.springframework.web.bind.annotation.ResponseBody; @Controller public class ExampleC { @RequestMapping("/firstApp") @ResponseBody public String firstSpringApp(){ return "Welcome!"; } }
- Update Maven configuration (install phase).
- Add the
@SpringBootApplication
annotation to your main application class.
- Add
SpringApplication.run(Main.class, args);
to yourmain
method.
<dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter</artifactId> <version>2.5.3</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> <version>2.5.3</version> </dependency> </dependencies>
- Create the
ExampleC
controller class as described in Approach 1.
Step 4: Running the Application
Click the green "Run" button in the toolbar. The console will display Tomcat startup information (port 8080).
Step 5: Viewing the Result
Access the application via your browser at http://localhost:8080/firstApp
. You should see "Welcome!".
Conclusion
IntelliJ IDEA significantly simplifies Spring Boot application development. Whether using Spring Initializr or a manual Maven setup, the process is streamlined, enabling efficient creation of robust and scalable applications. Leverage IntelliJ IDEA's features alongside Spring Boot's convention-over-configuration for optimal development.
The above is the detailed content of How to Run Your First Spring Boot Application in IntelliJ?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The key to writing PHP comments is to clarify the purpose and specifications. Comments should explain "why" rather than "what was done", avoiding redundancy or too simplicity. 1. Use a unified format, such as docblock (/*/) for class and method descriptions to improve readability and tool compatibility; 2. Emphasize the reasons behind the logic, such as why JS jumps need to be output manually; 3. Add an overview description before complex code, describe the process in steps, and help understand the overall idea; 4. Use TODO and FIXME rationally to mark to-do items and problems to facilitate subsequent tracking and collaboration. Good annotations can reduce communication costs and improve code maintenance efficiency.

Comments cannot be careless because they want to explain the reasons for the existence of the code rather than the functions, such as compatibility with old interfaces or third-party restrictions, otherwise people who read the code can only rely on guessing. The areas that must be commented include complex conditional judgments, special error handling logic, and temporary bypass restrictions. A more practical way to write comments is to select single-line comments or block comments based on the scene. Use document block comments to explain parameters and return values at the beginning of functions, classes, and files, and keep comments updated. For complex logic, you can add a line to the previous one to summarize the overall intention. At the same time, do not use comments to seal code, but use version control tools.

The key to writing good comments is to explain "why" rather than just "what was done" to improve the readability of the code. 1. Comments should explain logical reasons, such as considerations behind value selection or processing; 2. Use paragraph annotations for complex logic to summarize the overall idea of functions or algorithms; 3. Regularly maintain comments to ensure consistency with the code, avoid misleading, and delete outdated content if necessary; 4. Synchronously check comments when reviewing the code, and record public logic through documents to reduce the burden of code comments.

The key to writing PHP comments is clear, useful and concise. 1. Comments should explain the intention behind the code rather than just describing the code itself, such as explaining the logical purpose of complex conditional judgments; 2. Add comments to key scenarios such as magic values, old code compatibility, API interfaces, etc. to improve readability; 3. Avoid duplicate code content, keep it concise and specific, and use standard formats such as PHPDoc; 4. Comments should be updated synchronously with the code to ensure accuracy. Good comments should be thought from the perspective of others, reduce the cost of understanding, and become a code understanding navigation device.

The first step is to select the integrated environment package XAMPP or MAMP to build a local server; the second step is to select the appropriate PHP version according to the project needs and configure multiple version switching; the third step is to select VSCode or PhpStorm as the editor and debug with Xdebug; in addition, you need to install Composer, PHP_CodeSniffer, PHPUnit and other tools to assist in development.

PHP variables start with $, and the naming must follow rules, such as they cannot start with numbers and are case sensitive; the scope of the variable is divided into local, global and hyperglobal; global variables can be accessed using global, but it is recommended to pass them with parameters; mutable variables and reference assignments should be used with caution. Variables are the basis for storing data, and correctly mastering their rules and mechanisms is crucial to development.

There are three common ways to use PHP comments: single-line comments are suitable for briefly explaining code logic, such as // or # for the explanation of the current line; multi-line comments /*...*/ are suitable for detailed description of the functions or classes; document comments DocBlock start with /** to provide prompt information for the IDE. When using it, you should avoid nonsense, keep updating synchronously, and do not use comments to block codes for a long time.

The basic PHP syntax includes: 1. Use wrapping code; 2. Use echo or print to output content, where echo supports multiple parameters; 3. Variables do not need to declare types, start with $. Common types include strings, integers, floating-point numbers, booleans, arrays and objects. Mastering these key points can help you get started with PHP development quickly.
