Skip to content
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

Quarkus startup error logs seem to disapperar #135

Open
heineson opened this issue Jun 26, 2023 · 4 comments
Open

Quarkus startup error logs seem to disapperar #135

heineson opened this issue Jun 26, 2023 · 4 comments

Comments

@heineson
Copy link

Hello!

Really appreciating this plugin, makes migrating to Quarkus a lot easier for us in regards to log setup. I just noticed one thing however, which I can't see that it is my own fault. When enabling this plugin Quarkus startup errors seem to disapperar. Before adding the extension to our pom.xml, everything from Quarkus is logged as expected but after I just see nothing in the logs. Any idea what might be wrong?

Extension used:

    <dependency>
      <groupId>io.quarkiverse.logging.logback</groupId>
      <artifactId>quarkus-logging-logback</artifactId>
      <version>1.1.0</version>
    </dependency>

Expected error in log:

2023-06-26 11:06:16,080 ERROR io.quarkus.runtime.Application - Failed to start application (with profile [dev]): ...

@GinaGeorgescul
Copy link

Hello! Wondering if there is any fix planned for this issue?

@gsmet
Copy link
Member

gsmet commented Aug 29, 2023

Isn't slf4j-jboss-logmanager in our BOM? I'm surprised you have to manage the version yourself?

@GinaGeorgescul
Copy link

It is, and for me overriding it with a different version did not fix the issue.
Hibernate startup validation failure is still not logged.

The extension used is: <dependency> <groupId>io.quarkiverse.logging.logback</groupId> <artifactId>quarkus-logging-logback</artifactId> <version>0.13.0</version> </dependency> I tried overriding the 1.2.0.Final slf4j-jboss-logmanager with 2.0.1.Final

@gsmet
Copy link
Member

gsmet commented Aug 29, 2023

I don't think I will have the cycles to look into this anytime soon so I would recommend you all have a look with a debugger and try to understand what's going on.
Might not be easy though, I have no idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants