I started seeing unexpected logs after upgrading Spring Boot from version 3.3.4 to 3.4.0.

Skipping search for files matching pattern [**/*.class]: directory [/Users/core/workspace/me/projects/samples/test/dependencies/build/classes/java/main/me/choicore/samples/test/api] does not exist
rootPorject
ㄴ applicaion-module
    ㄴ src
        ㄴmain
            ㄴ java
                ㄴ me/choicore/samples/test
                    ㄴ api
                        ㄴ Application.java (entrypoint)
ㄴ dependencies-module
    ㄴ src
        ㄴ main
            ㄴ java
                ㄴ me/choicore/samples/test
                    ㄴ dependencies
...

Spring PathMatchingResourcePatternResolver should not log directory-skip messages at info level

The project is set up as a multi-module structure, and as shown in the image, the entry point is located under the API package.

Spring PathMatchingResourcePatternResolver should not log directory-skip messages at info level

After analyzing line 695 of PathMatchingResourcePatternResolver.class, I found a process that creates sub-resources. While the dependencies-module doesn't contain a package named 'api', related logs are being generated. Although the application starts up normally, these logs keep appearing. If this is intended behavior, shouldn't we consider adjusting the logging level

If analysis is needed, I will attach a test project.

Comment From: jhoeller

Good point, we should switch to debug log level there.

Comment From: CHOICORE

Good point, we should switch to debug log level there.

Submitted a pull request for this simple fix.

fixed #33956

Comment From: snicoll

Closing in favor of PR https://github.com/spring-projects/spring-framework/pull/33956