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

Flyway is not instantiated by using Named annotation #623

Closed
lucaguada opened this issue Feb 1, 2017 · 0 comments
Closed

Flyway is not instantiated by using Named annotation #623

lucaguada opened this issue Feb 1, 2017 · 0 comments
Labels
Milestone

Comments

@lucaguada
Copy link

It's not possible to use different instances of Flyway, since the names specified in the following code:

{
...use(new Flywaydb("flyway.db1");
...use(new Flywaydb("flyway.db2");
}

are always ignored and Jooby (or rather Guice) complains about multiple bindings of Flyway:

A binding to org.flywaydb.core.Flyway was already configured at org.jooby.flyway.Flywaydb.configure(Flywaydb.java:183).

@lucaguada lucaguada changed the title Flywaydb is not instantiated by using Named annotation Flyway is not instantiated by using Named annotation Feb 1, 2017
@jknack jknack added the bug label Feb 2, 2017
@jknack jknack added this to the 1.0.3 milestone Feb 2, 2017
@jknack jknack modified the milestones: 1.1.0, 1.0.3 Feb 8, 2017
@jknack jknack closed this as completed in 819ba0a Feb 13, 2017
jknack added a commit that referenced this issue Feb 13, 2017
Flyway is not instantiated by using Named annotation fix #623
@jknack jknack modified the milestones: 1.0.3, 1.1.0 Feb 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants