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
NullPointerException at org.flywaydb.maven.MigrateMojo.doExecute(MigrateMojo.java:35) #905
Comments
Looking at the code (and my project) I think this exception is caused by the fact that Flyway assumes at least one migration will be found. You probably need to add an explicit check in case no migrations are found. |
Uh oh, that's never good. Consider this fixed in time for the next release. Pull request also welcome. |
Hi, Is there anyway I can help you with this ? Im trying to get it working, and it's really annoying that it wont work right out of the box. I guess I can manually add the entry to the table, but I was wondering if I can help you in here. |
This bug is happening in Flyway 3.2.1. |
@MrEcko Please verify the stacktrace to make sure it is the same problem. If it isn't, please open a separate issue. Cheers |
It is the same On a side note, i got to this by going with the default sqlMigrationPrefix but naming the migrations with v (lower case). Worked after prefixing the files with V.
|
Good catch! Reopening. Thanks. |
Fixed. |
Flyway 3.1
Output:
I assume this is triggered by user error, but Flyway shouldn't be throwing an exception.
The text was updated successfully, but these errors were encountered: