flywaydb is not even as good as pure SQL scripts. It is mainly designed to be a forward-only tool. I honestly doubt anyone with some database background would recommend it.
Well, I have DB background. I've designed the schema for a moderately large OTA (tingo.com) where I've used Flyway, and I would recommend and use Flyway. Forward only migrations aren't bad, and work pretty well in the real world. As some else pointed out, there are situations (like drop table) that cannot be reversed.
As long as each release is backwards compatible with the previous one, you won't ever need to roll back.
We use it at work, and it works decently. For our development model, we don't need something more complex, and the possibility to have code-based migrations is important (don't know if you can get that with Liquidbase).
As long as each release is backwards compatible with the previous one, you won't ever need to roll back.