Pfthb

I can access the controller in web browser, but I can't see its mapping message in the console log. Normally when spring boot app starts, the eclipse console should print out the mapped controller and the accessing url, why didn't I see it?

I have already added the logging.level.org.springframework.web=DEBUG to application.properties file, but it does not help.

Updated:
This is my pom.xml file:

<modelVersion>4.0.0</modelVersion>

<groupId>com.yp</groupId>
<artifactId>BootTest</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

<name>BootTest</name>
<description>Demo project for Spring Boot</description>

<parent>
 <groupId>org.springframework.boot</groupId>
 <artifactId>spring-boot-starter-parent</artifactId>
 <version>2.1.0.RELEASE</version>
 <relativePath/> <!-- lookup parent from repository -->
</parent>

<properties>
 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
 <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
 <java.version>1.8</java.version>
</properties>

<dependencies>
 <dependency>
 <groupId>org.springframework.boot</groupId>
 <artifactId>spring-boot-starter-web</artifactId>
 </dependency>

 <dependency>
 <groupId>org.springframework.boot</groupId>
 <artifactId>spring-boot-starter-test</artifactId>
 <scope>test</scope>
 </dependency>
</dependencies>

<build>
 <plugins>
 <plugin>
 <groupId>org.springframework.boot</groupId>
 <artifactId>spring-boot-maven-plugin</artifactId>
 </plugin>
 </plugins>
</build>

The snippet of console log when app starts

Is there any way to show up mapped controller info when app starts?

As mentioned by Andy Wilkinson there has been a lot of overhaul especially in terms of logging. The commit removed the log.

If you wish to see this information, you can change the logging level to TRACE instead of falling back to a previous version

logging.level.org.springframework.web: TRACE

Just add this -Ddebug in the eclipse VM arguments and the detailed debug logs will start printing.

Just like the comment post by Andy Wilkinson said, I was using spring boot 2.1, when I change the spring boot version to older one, this issue doesn't happen again.