After having lots of trouble getting flyway to work with heroku's postgres plugin, I decided I needed to be able to tweak flyway's slf4j logging to figure out what is going on.
This PR adds that capability to your wrapper.
I decided to just pick one slf4j implementation instead of making the config more complex and allowing people to pick whatever slf4j implementation they wanted. I chose the jdk logger (instead of log4j, jcl, simple, etc.) because it was small and self contained.
After having lots of trouble getting flyway to work with heroku's postgres plugin, I decided I needed to be able to tweak flyway's slf4j logging to figure out what is going on.
This PR adds that capability to your wrapper.
I decided to just pick one slf4j implementation instead of making the config more complex and allowing people to pick whatever slf4j implementation they wanted. I chose the jdk logger (instead of log4j, jcl, simple, etc.) because it was small and self contained.