When running the validate operation from the command line, validation errors are omitted from the output. This is due to the printDescriptiveError method in the ValidationFailedException [1] simply not printing errors as it should (compare to the getMessage [2] method – the last two blocks are missing). This could probably be simplified/standardized to write the result of getMessage to avoid having to maintain two blocks of nearly identical code.
This is rendering the command useless from the CLI, as the output does not indicate anything other than that there are some unknown validation errors. For example:
When running the validate operation from the command line, validation errors are omitted from the output. This is due to the
printDescriptiveErrormethod in theValidationFailedException[1] simply not printing errors as it should (compare to thegetMessage[2] method – the last two blocks are missing). This could probably be simplified/standardized to write the result of getMessage to avoid having to maintain two blocks of nearly identical code.This is rendering the command useless from the CLI, as the output does not indicate anything other than that there are some unknown validation errors. For example:
[1] https://github.com/liquibase/liquibase/blob/3.8.x/liquibase-core/src/main/java/liquibase/exception/ValidationFailedException.java#L127
[2] https://github.com/liquibase/liquibase/blob/3.8.x/liquibase-core/src/main/java/liquibase/exception/ValidationFailedException.java#L98