Jacek Gębal

I am having a second thought now. To achieve this, you can simply call the setup inside a test, if the setup is test-specific. so instead of: ```sql create or...

@hkyle The main benefit of having beforetest/aftertest invoked from the framework than from within test procedure is that it will be executed outside of the test and that it will...

This was raised as a question from [JetBrains](https://youtrack.jetbrains.com/issue/DBE-9671#focus=streamItem-27-3991298.0-0)

What is it that you would like to achieve exactly? Current implementation of utPSLQL implicitly excludes unit test packages from coverage as far as I remember. If you are using...

Hi @wolframhaussig I one more option that could work for you. You can annotate each non-reported code using `--%suite`. This way the code will not be included in coverage report...

You can create a version in github Each version can have supported DB list. So older version of DB could be using older scripts while with newer versions you only...

I have tried using `${path.separator}` instead of `:` and `${file.separator}` instead of `/` in the `pom` file But still get the same error, even thought the Windows-style path looks good....

After I have disabled the entire `` section it began to work. ```xml ```

``` [2/7] Performing analysis... [*******] (42.1s @ 4.32GB) 20,565 (94.63%) of 21,733 classes reachable 36,962 (66.44%) of 55,631 fields reachable 109,625 (68.59%) of 159,829 methods reachable 12,304 ( 7.70%) of...

Well, that was not so good either. The EXE build ok but it doesn't really work. ``` C:\Users\JacekGebal>cd DataGripProjects\plsql-formatter-settings\standalone\target C:\Users\JacekGebal\DataGripProjects\plsql-formatter-settings\standalone\target>tvdformat.exe ACCOUNT.sql Exception in thread "main" javax.script.ScriptException: org.graalvm.polyglot.PolyglotException: SyntaxError: :1:0 Expected...