Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support option to use Slf4j/Commons Logging/JUL when using the command line tool #1075

Closed
ericparton opened this issue Aug 9, 2015 · 3 comments

Comments

@ericparton
Copy link

Currently, when using the command line tool, Flyway only supports logging to standard out. It would be useful if the command line tool could optionally leverage Flyway's existing ability to use Slf4j or Commons Logging if their jars are on the classpath.

@axelfontaine
Copy link
Contributor

Thanks for your suggestion. What would be the real world use case for this?

Cheers
Axel

@ericparton
Copy link
Author

It would allow users of the command line tool to log the output of the tool to a file on disk if a jar with a logging configuration file and the logging jars were on the classpath. You could also do things like configure the logger to print the info statements to the console, but only log the debug statements to a file, so you don't have to run the tool with the debug flag and you still have the ability to consult the logs if there's an issue.

Thanks,
Eric

axelfontaine pushed a commit to flyway/flywaydb.org that referenced this issue Oct 1, 2015
@axelfontaine
Copy link
Contributor

I ended up implementing it with an automatic switch instead.

Cheers
Axel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants