-
Notifications
You must be signed in to change notification settings - Fork 40.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mvn spring-boot:run doesn't run a Spring Boot App but always success #34467
Comments
It could be possible that you hit #34379. If this isn't it, please attach a sample application so that we can take a look at it. |
@mhalbritter I have tried downgrading but using spring boot 3.0.2 and spring framework 6.0.4 still doesn't work. I also tried using Maven with trace level logging enabled: |
It doesn't look like you have a space in your directory structure, so I don't think it's #34379. From the logs, it looks like the application either isn't ran, or it runs and exits immediately. Does you application work if you run the main method from an IDE? |
@philwebb I'm trying to run our app's main method from Intellij, it shows:
|
That looks like your application's main method hasn't done anything. Perhaps you can step through it in the debugger to determine what's happening. |
Thank you @wilkinsona, I debugged on the main method in intellij, and it deplayed the error: |
We used ch.qos.logback:logback-classic:1.2.11 before, should we upgrade for spring boot 3.0.x? |
Yes. Please use the 1.4.x version that's provided by Spring Boot's dependency management. You should also use SLF4J 2.0.x rather than 1.7.x. I'm going to close this issue now as it appears to be caused by trying to use unsupported dependency versions. |
@wilkinsona where can I find the spring boot's dependency management? |
Either by using |
Hello Spring Team,
After upgrading spring boot from
2.7.7
to3.0.3
, I cannot run the service withmvn spring-boot:run -X
, the result is always success but the spring boot app is not started. Attached the mvn debug logs for analysis: log.txtI didn't find any useful clues from the logs, do I miss some configurations or can we do something for digging out the issue?
The text was updated successfully, but these errors were encountered: