Combining -json and -logFile yields no logFile

Which version and edition of Flyway are you using?

6.1.0

If this is not the latest version, can you reproduce the issue with the latest one as well?

(Many bugs are fixed in newer releases and upgrading will often resolve the issue)

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Command-line

Which database are you using (type & version)?

MSSQL 2017 CU17 in Docker

Which operating system are you using?

MacOS

What did you do?

(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.) flyway info -json -logFile=“test”

What did you expect to see?

A test file created with JSON formatting of the output

What did you see instead?

Nothing. -json and -logFile function independently, but they do not function together. Instead, JSON formatting is printed to standard out, but the log file is not created.

[juliahayward]

OK, we’ve discussed and the conclusion we’ve come to is:

• use -outputFile in preference to -logFile (though the latter will persist as a deprecated, undocumented option for people who picked it up early, at least for now)
• when -json is turned on, you get nothing but the JSON object as output (a fatal error being part of the object). -X doesn’t change this.
• when -outputFile is turned on, the output file gets a verbatim copy of the console output regardless of -json

[alextercete]

Another thing is that -q should suppress output (apart for warnings and errors) from both the console and the file. However, all command-line options that set log level (namely -q and -X) should be ignored when -json is specified.