-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Print logs on ChangeSet exception #2354
Comments
Thanks for taking the time to submit this detail @maxencelaurent . We are reviewing and will get back to you. |
@maxencelaurent: |
The Liquibase CDI integration needs some love from QA. Instead of blocking this PR from merging until a full/official certification of Liquibase CDI completes, @nvoxland added a new integration test, I am comfortable with merging this PR, especially given that @maxencelaurent collaborated with Nathan and feels this PR will address the immediate need. Moving to ready to merge. |
Environment
Liquibase Version: 4.7.0 with CDI Plugin
Liquibase Integration & Version:
Liquibase Extension(s) & Version: any
Database Vendor & Version: any
Operating System Type & Version: any
Description
Despite LiquiBase logs plenty of information, there is not a single statement about exceptions which may occur when applying changesets (FINE level set for all LiquiBase loggers).
The current behaviour is to simply throw exceptions, without any logs.
When Liquibase is run in a CDI environment (weld, in my case), there is no way to understand what's wrong as the only relevant log statement is:
Steps To Reproduce
Actual Behavior
Liquibase does not log any relevant information about what failed.
Only way to understand underlying errors is to use a debugger...
Expected/Desired Behavior
Big fat error message which explain what's wrong
The text was updated successfully, but these errors were encountered: