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

Log the inner exception thrown from JdbcMigrationResolver.resolveMigrations() #1396

Closed
logicbomb opened this issue Aug 7, 2016 · 0 comments
Milestone

Comments

@logicbomb
Copy link

What version of Flyway are you using?

4.03

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

Command-line

What database are you using (type & version)?

Postgres 9.4

What operating system are you using?

Ubuntu 14.04

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Attempted to execute a java migration

What did you expect to see?

Helpful error message

What did you see instead?

ERROR: Unable to resolve Jdbc Java migrations in location: classpath:db/migration

It would be nice if flyway logged the inner exception thrown from JdbcMigrationResolver.resolveMigrations() I'm sure a lot of Java migration errors are a result of the java implementation and nothing to do with Flyway, but as it stands now it's tough to have any idea what's going on. Even changing the error message to include (something like) "try re-running the migration with the -X switch to see detailed logs" would be a big help.

@axelfontaine axelfontaine changed the title Errors in java migrations are very difficult to debug Invite users to use -X switch in case of error Aug 8, 2016
@axelfontaine axelfontaine changed the title Invite users to use -X switch in case of error Log the inner exception thrown from JdbcMigrationResolver.resolveMigrations() Feb 7, 2017
@axelfontaine axelfontaine added this to the Flyway 4.1 milestone Feb 7, 2017
axelfontaine pushed a commit to flyway/flywaydb.org that referenced this issue Feb 7, 2017
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