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

Warn instead of fail when a location is not found #477

Closed
flyway opened this issue Jun 25, 2013 · 1 comment
Closed

Warn instead of fail when a location is not found #477

flyway opened this issue Jun 25, 2013 · 1 comment
Labels
Milestone

Comments

@ghost
Copy link
Collaborator

@ghost ghost commented Jun 25, 2013

Original author: michael....@gmail.com (April 22, 2013 06:39:24)

After the upgrade from Flyway 1.7 to 2.1.1 we get for not used directories the following error: "FlywayException: Unable to determine URL for classpath location"

We have empty directories because we use one Flayway configuration file for different project configuration. And not all projects needs all of this directories. So is it possible to change this error to a warning?

Best regards
Michael

Original issue: http://code.google.com/p/flyway/issues/detail?id=479

@alsha
Copy link

@alsha alsha commented Jul 26, 2013

It is really annoying problem. I am using flyway to do migrations automatically on web application start-up. This error prevents application to initialize.
Workaround: dummy-file in each directory (specified as flyway-location)....

@axelfontaine axelfontaine added this to the Flyway 4.0 milestone Nov 25, 2014
@axelfontaine axelfontaine changed the title Change error "FlywayException: Unable to determine URL for classpath location: ..." to a warning Warn instead of fail when a location is not found Dec 29, 2015
axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Dec 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.