You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently installing our sources with Liquibase via Maven.
In some of our files ( grants, synonyms mostly) we use palceholders so we can dynamicly change the statement.
Now in Jenkins when analyzing the sources, we get errors like this:
[Build develop] ERROR: Parse error at line 1 column 27:
[Build develop]
[Build develop] --> grant all on <table> to ${project_user};
Is there a way to work around this ?
Regards,
Kim
The text was updated successfully, but these errors were encountered:
Short answer: with the current release there's no way to work around this.
But... I've just added an error recovery mechanism to the parser. Starting from the next version, the analysis will try to ignore unrecognized commands instead of breaking the analysis of the whole file.
Please see this example:
Note that even with the invalid command, the parser was able to continue the analysis and it registered the violations.
We are currently installing our sources with Liquibase via Maven.
In some of our files ( grants, synonyms mostly) we use palceholders so we can dynamicly change the statement.
Now in Jenkins when analyzing the sources, we get errors like this:
Is there a way to work around this ?
Regards,
Kim
The text was updated successfully, but these errors were encountered: