dropwizard / dropwizard-flyway Goto Github PK

View Code? Open in Web Editor NEW

61.0 61.0 27.0 1.77 MB

Addon bundle for Dropwizard to support Flyway for database migrations

Home Page: https://dropwizard.github.io/dropwizard-flyway/

License: Apache License 2.0

Java 100.00%

database-migrations dropwizard flyway

dropwizard-flyway's Introduction

Dropwizard

Dropwizard is a sneaky way of making fast Java web applications.

It's a little bit of opinionated glue code which bangs together a set of libraries which have historically not sucked:

Jetty for HTTP servin'.
Jersey for REST modelin'.
Jackson for JSON parsin' and generatin'.
Logback for loggin'.
Hibernate Validator for validatin'.
Metrics for figurin' out what your application is doin' in production.
JDBI and Hibernate for databasin'.
Liquibase for migratin'.

Want to contribute to Dropwizard?

Before working on the code, if you plan to contribute changes, please read the following CONTRIBUTING document.

Need help or found an issue?

When reporting an issue through the issue tracker on GitHub or sending an email to the Dropwizard User Google Group mailing list, please use the following guidelines:

Check existing issues to see if it has been addressed already
The version of Dropwizard you are using
A short description of the issue you are experiencing and the expected outcome
Description of how someone else can reproduce the problem
Paste error output or logs in your issue or in a Gist. If pasting them in the GitHub issue, wrap it in three backticks: ``` so that it renders nicely
Write a unit test to show the issue!

dropwizard-flyway's People

Contributors

Stargazers

Watchers

dropwizard-flyway's Issues

Warning: Direct configuration of the Flyway object has been deprecated

This warning is pretty many times in the logs:

org.flywaydb.core.Flyway - Direct configuration of the Flyway object has been deprecated and will be removed in Flyway 6.0. Use Flyway.configure() instead.

I'm using version 1.3.0-4

Command line arguments

    <dependency>
        <groupId>io.dropwizard</groupId>
        <artifactId>dropwizard-db</artifactId>
        <version>0.8.0</version>
    </dependency>
    <dependency>
        <groupId>io.dropwizard.modules</groupId>
        <artifactId>dropwizard-flyway</artifactId>
        <version>0.8.0-1</version>
        <exclusions>
            <exclusion>
                <artifactId>dropwizard-db</artifactId>
                <groupId>io.dropwizard</groupId>
            </exclusion>
        </exclusions>
    </dependency>

Can you provide some examples of using Flyway commands in the readme?

I tried:

db info config.yml
-> invalid choice: 'config.yml' (choose from 'clean', 'info', 'init', 'migrate', 'repair', 'validate')
db config.yml info
-> default configuration has an error: * Unrecognized field at:
db config.yml info server
-> file not found server
server config.yml db info
-> unrecognized arguments: 'db info'

Plans for new release?

The last release has been published on 7 Jul 2018. Are there any plans to publish a new release anytime soon? I'm asking since flyway-core has been upgraded in the meantime.

Support for EnvironmentVariableSubstitutor?

Dropwizard supports sourcing of environment variables. Since the Flyway CLI command does not run the Application, it does not know about a configured EnvironmentVariableSubstitutor.

Is it possible to source environment variables to be used in the YAML configuration file when a CLI command like db info is issued?

Flyway configs overwritten by defaults

The issue is with this code: https://github.com/dropwizard/dropwizard-flyway/blob/master/src/main/java/io/dropwizard/flyway/cli/DbMigrateCommand.java#L67-L86

    @Override
    public void run(final Namespace namespace, final Flyway flyway) throws Exception {
        final Boolean outOfOrder = namespace.getBoolean(OUT_OF_ORDER);
        final Boolean validateOnMigrate = namespace.getBoolean(VALIDATE_ON_MIGRATE);
        final Boolean cleanOnValidationError = namespace.getBoolean(CLEAN_ON_VALIDATION_ERROR);
        final Boolean baselineOnMigrate = namespace.getBoolean(INIT_ON_MIGRATE);

        if (outOfOrder != null) {
            flyway.setOutOfOrder(outOfOrder);
        }

        if (validateOnMigrate != null) {
            flyway.setValidateOnMigrate(validateOnMigrate);
        }

        if (cleanOnValidationError != null) {
            flyway.setCleanOnValidationError(cleanOnValidationError);
        }

        if (baselineOnMigrate != null) {
            flyway.setBaselineOnMigrate(baselineOnMigrate);
        }

        final int successfulMigrations = flyway.migrate();
        LOG.debug("{} successful migrations applied", successfulMigrations);
    }

namespace contains a list of parameters and their defaults, the flyway instance already has the configurations loaded into it, but the lines here overwrite that configuration with the default values.

I'm trying to set validateOnMigrate to true, but it always gets overwritten. I'm running the migrate task through gradle.

task flywayMigrate(type: JavaExec) {
  classpath = sourceSets.main.runtimeClasspath

  main = mainClassName

  args 'db', 'migrate', "$project.projectDir/config.yml"
}

Allow Out of Order DB Migration Configuration

@joschi

We want to more or less be able to implement this procedure on our team (tl;dr version numbers are timestamps and we allow out of order migrations on dev machines to avoid branch hell): http://www.jeremyjarrell.com/using-flyway-db-with-distributed-version-control/

It looks to me like this would be accomplished by putting an option on FlywayConfiguration and then just setting the option in FlywayFactory. If that's all that's needed, I'm happy to submit a PR to do it.

Doesn't work with SQLite

I'm using io.dropwizard:dropwizard-core:0.7.0, io.dropwizard.modules:dropwizard-flyway:0.7.0-1, and org.xerial:sqlite-jdbc:3.8.7

The database configuration looks like this

# Database settings
database:
  # the name of your JDBC driver
  driverClass: org.sqlite.JDBC

  # the JDBC URL
  url: jdbc:sqlite:dev.db

  # the JDBC user
  user: jhutchins

When trying to run a migrate command

java -jar application/build/libs/application-all-0.1.0.jar db migrate ./dev.yml

I get the following output

INFO  [2015-01-01 18:02:00,397] org.flywaydb.core.internal.dbsupport.DbSupportFactory: Database: jdbc:sqlite:dev.db (SQLite 3.0)
INFO  [2015-01-01 18:02:00,581] org.flywaydb.core.internal.command.DbMigrate: Current version of schema "main": << Empty Schema >>
INFO  [2015-01-01 18:02:00,581] org.flywaydb.core.internal.command.DbMigrate: Migrating schema "main" to version 1
Exception in thread "main" org.flywaydb.core.api.FlywayException: Unable to commit transaction
    at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:76)
    at org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:285)
    at org.flywaydb.core.internal.command.DbMigrate.access$800(DbMigrate.java:46)
    at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:207)
    at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:156)
    at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)
    at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:156)
    at org.flywaydb.core.Flyway$1.execute(Flyway.java:864)
    at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
    at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
    at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
    at io.dropwizard.flyway.cli.DbMigrateCommand.run(DbMigrateCommand.java:76)
    at io.dropwizard.flyway.cli.DbCommand.run(DbCommand.java:48)
    at io.dropwizard.flyway.cli.AbstractFlywayCommand.run(AbstractFlywayCommand.java:45)
    at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76)
    at io.dropwizard.cli.Cli.run(Cli.java:70)
    at io.dropwizard.Application.run(Application.java:72)
    at com.nti.flow.Flow.main(Flow.java:29)
ERROR [2015-01-01 18:02:06,606] org.flywaydb.core.internal.util.jdbc.TransactionTemplate: Unable to restore autocommit to original value for connection
! java.sql.SQLException: database is locked
! at org.sqlite.core.DB.throwex(DB.java:859) ~[application-all-0.1.0.jar:0.1.0]
! at org.sqlite.core.DB.exec(DB.java:142) ~[application-all-0.1.0.jar:0.1.0]
! at org.sqlite.jdbc3.JDBC3Connection.setAutoCommit(JDBC3Connection.java:152) ~[application-all-0.1.0.jar:0.1.0]
! at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0]
! at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0]
! at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0]
! at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
! at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126) ~[application-all-0.1.0.jar:0.1.0]
! at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) ~[application-all-0.1.0.jar:0.1.0]
! at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80) ~[application-all-0.1.0.jar:0.1.0]
! at com.sun.proxy.$Proxy28.setAutoCommit(Unknown Source) ~[na:na]
! at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:96) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:285) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate.access$800(DbMigrate.java:46) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:207) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:156) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:156) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway$1.execute(Flyway.java:864) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway$1.execute(Flyway.java:811) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway.execute(Flyway.java:1171) [application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway.migrate(Flyway.java:811) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.flyway.cli.DbMigrateCommand.run(DbMigrateCommand.java:76) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.flyway.cli.DbCommand.run(DbCommand.java:48) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.flyway.cli.AbstractFlywayCommand.run(AbstractFlywayCommand.java:45) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.cli.Cli.run(Cli.java:70) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.Application.run(Application.java:72) [application-all-0.1.0.jar:0.1.0]
! at com.nti.flow.Flow.main(Flow.java:29) [application-all-0.1.0.jar:0.1.0]
Caused by: java.sql.SQLException: database is locked
    at org.sqlite.core.DB.throwex(DB.java:859)
    at org.sqlite.core.DB.exec(DB.java:142)
    at org.sqlite.jdbc3.JDBC3Connection.commit(JDBC3Connection.java:162)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
ERROR [2015-01-01 18:02:06,607] org.flywaydb.core.internal.command.DbMigrate: Migration of schema "main" to version 1 failed! Changes successfully rolled back.
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
    at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)
    at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80)
    at com.sun.proxy.$Proxy28.commit(Unknown Source)
    at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:73)
    ... 17 more
ERROR [2015-01-01 18:02:06,607] io.dropwizard.flyway.cli.AbstractFlywayCommand: Error while running database command
! java.sql.SQLException: database is locked
! at org.sqlite.core.DB.throwex(DB.java:859) ~[application-all-0.1.0.jar:0.1.0]
! at org.sqlite.core.DB.exec(DB.java:142) ~[application-all-0.1.0.jar:0.1.0]
! at org.sqlite.jdbc3.JDBC3Connection.commit(JDBC3Connection.java:162) ~[application-all-0.1.0.jar:0.1.0]
! at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0]
! at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0]
! at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0]
! at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
! at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126) ~[application-all-0.1.0.jar:0.1.0]
! at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109) ~[application-all-0.1.0.jar:0.1.0]
! at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80) ~[application-all-0.1.0.jar:0.1.0]
! at com.sun.proxy.$Proxy28.commit(Unknown Source) ~[na:na]
! at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:73) ~[application-all-0.1.0.jar:0.1.0]
! ... 17 common frames omitted
! Causing: org.flywaydb.core.api.FlywayException: Unable to commit transaction
! at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:76) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:285) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate.access$800(DbMigrate.java:46) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:207) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:156) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:156) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway$1.execute(Flyway.java:864) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway$1.execute(Flyway.java:811) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway.execute(Flyway.java:1171) ~[application-all-0.1.0.jar:0.1.0]
! at org.flywaydb.core.Flyway.migrate(Flyway.java:811) ~[application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.flyway.cli.DbMigrateCommand.run(DbMigrateCommand.java:76) ~[application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.flyway.cli.DbCommand.run(DbCommand.java:48) ~[application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.flyway.cli.AbstractFlywayCommand.run(AbstractFlywayCommand.java:45) ~[application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.cli.Cli.run(Cli.java:70) [application-all-0.1.0.jar:0.1.0]
! at io.dropwizard.Application.run(Application.java:72) [application-all-0.1.0.jar:0.1.0]
! at com.nti.flow.Flow.main(Flow.java:29) [application-all-0.1.0.jar:0.1.0]

ALTER COLUMN in Redshift is killing me

I have a deploy and I can't deploy because of this issue.

[Amazon](500310) Invalid operation: ALTER TABLE ALTER COLUMN cannot run inside a transaction block;

This requires using flyway release 6. I can't just add the dependency because a constructor has changed. How soon until a new release? Or is there some other workaround until then?

Run commands via configuration

I end up needing to fork this project since most of my projects use a service wrapper (ie. tanuki). The problem is that I am unable to run cli commands directly in the dropwizard server console, since the output is throttled to a file for logging.

In my fork I have the ability to set preconfigured commands to be run every time on startup (like migrate) to assure the system is up to date when I deploy a new version through CI. Decoupling this with the conceptual run command for the dropwizard server seems a bit cleaner as well.

I am more than happy to contribute these changes as a second bundle on top of the default one or alter the current one to allow both forms of commands to be run.

Thoughts? Concerns?

Update to Flyway 5.0.7

This should be trivial as the public API hasn't changed much at all. See https://flywaydb.org/documentation/releaseNotes#5.0.0

Support for flyway configs through FlywayFactory specifically `baselineVersion`

This is a pretty simple feature request which I'll make patchset for.

org.flywaydb.core.Flyway supports more configuration options than are exposed through io.dropwizard.flyway.FlywayFactory. I'd like to see those added, specifically the baselineVersion option.

How to know what flyway version to use

The docs cleary states that if I am using Mysql, I also need to add something like

    implementation 'org.flywaydb:flyway-mysql:$flyway.version'

But how do I know what flyway.version to use? I can see that version 3.0.0-4 (for Dropwizard 3) of this module is using flyway version 9.22.3, but how can I keep these versions in sync as I upgrade this module? Do I always have to check it manually or can it be linked somehow? I am using dependabot to keep track of updates.

Supported Command Configuration

Hi @joschi

Is it possible to add a configuration section that lists the allowed/supported commands that can be run with the db command? My thinking is to make sure that certain commands like clean, etc. are not run in production environment by mistake.

I'm thinking something like adding a section that list all the supported commands for the environment. i.e.

  commands: migrate, info, validate, repair

with default being all commands i.e. migrate, clean, info, validate, baseline, repair are allowed. And the implementation checks if the command is allowed before executing it.

Obviously this can be implemented the other way around by adding a disallowed/banned commands section where only those commands that are not allowed are listed.

Finally may be migrate and info should always be allowed because what would be the point of using flyway if not for migration?

What do you think?

respect baselineOnMigrate set through config file

I'm wondering if

dropwizard-flyway/src/main/java/io/dropwizard/flyway/cli/DbMigrateCommand.java

Line 74 in 7544dfe

flyway.setBaselineOnMigrate(namespace.getBoolean(INIT_ON_MIGRATE));

is intentional. I was trying to pass baselineOnMigration in my config file but it gets overridden due to the lack of --initOnMigrate in CLI. the CLI command I'm using needs to work for both flyway migrations and dropwizard migrations so I have less wiggle room to customize it.

Failed to parse configuration at: flyway.schemas;

Hi,

I'm seeing this error:

Can not deserialize instance of java.util.ArrayList out of VALUE_STRING token
at [Source: N/A; line: -1, column: -1] (through reference chain:

Configuration["flyway"]->io.dropwizard.flyway.FlywayFactory["schemas"])

Thanks,
-Gnana

Connection retries configuration

It seems it is not possible to configure flyway connectRetries with the Dropwizard configuration.

https://flywaydb.org/documentation/configuration/parameters/connectRetries

There is also a related setting connectRetriesInterval

https://flywaydb.org/documentation/configuration/parameters/connectRetriesInterval

Support defining flyway properties in Configuration

There are several different properties for Flyway. Would be nice if I could define this in my YAML file.

Upgrade to Dropwizard 3.0: Incompatibility with Flyway-Bundle

We are looking to upgrade our applications to Dropwizard 3.0, however, it is currently not possible due to a dependency on the flyway bundle that only supports Dropwizard 2.x.

Flyway 4.0.2 released

https://flywaydb.org/documentation/releaseNotes

Whats the update policy anyway? Update when time permits it? :D

How to resolve PostgreSQL Transactional Lock issue using dropwizard-flyway

Hi there,

in our project we use dropwizard-flyway for our database migrations.
We would like to upgrade to the Dropwizard 4.x and we're isuued with the problem during migration scripts execution migration, that is mentioned flyway/flyway#3508
There is known solution for this problem https://documentation.red-gate.com/fd/postgresql-transactional-lock-184127530.html but i'm still confused how to apply those additional settings tvia dropwizard-flyway library.

Thank you in advance

[question] how should I go about supporting migrating more than one database

what's a good way to support migrating a number of DataSourceFactory in one DW service? I can probably add multiple FlywayBundle when overriding Application#initialize, but I don't know if this plugin supports picking the right DataSourceFactory to migrate via CLI args.

a workaround I can employ is to have one config file per database (having a different url) and pass that along when starting the app for migration, but the application would have to know how to pick the right set of migration files to apply under db/migrate which I'm not sure how to achieve.

Use updated flyway_schema_history table name

flyway changed the name of the schema history table from schema_version to flyway_schema_history from v5.0.0 onwards. Your FlywayFactory class still seems to use the old name (line 28 - private String metaDataTableName = "schema_version";).

This causes the following warning to be logged when validating the schema:

WARN JdbcTableSchemaHistory:53 - Could not find schema history table my_db.flyway_schema_history, but found my_db.schema_version instead. You are seeing this message because Flyway changed its default for flyway.table in version 5.0.0 to flyway_schema_history and you are still relying on the old default (schema_version). Set flyway.table=schema_version in your configuration to fix this. This fallback mechanism will be removed in Flyway 6.0.0.

I know that I can override this default by adding this to my dropwizard YML file:

flyway:
metaDataTableName: flyway_schema_history

But I was wondering if this default can be changed to match the current flyway default?

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

WARN: Base branch does not exist - skipping

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

Branch release/2.1.x

github-actions

.github/workflows/build.yml

dropwizard/workflows main

dropwizard/workflows main

.github/workflows/release.yml

dropwizard/workflows main

.github/workflows/trigger-release.yml

dropwizard/workflows main

maven

pom.xml

io.dropwizard.modules:module-parent 2.1.2

org.flywaydb:flyway-core 10.17.1

org.flywaydb:flyway-database-postgresql 10.17.1

com.h2database:h2 2.3.232

maven-wrapper

.mvn/wrapper/maven-wrapper.properties

maven 3.9.9

Branch release/3.0.x

github-actions

.github/workflows/build.yml

dropwizard/workflows main

dropwizard/workflows main

.github/workflows/release.yml

dropwizard/workflows main

.github/workflows/trigger-release.yml

dropwizard/workflows main

maven

pom.xml

io.dropwizard.modules:module-parent 3.0.2

org.flywaydb:flyway-core 10.17.1

org.flywaydb:flyway-database-postgresql 10.17.1

com.h2database:h2 2.3.232

maven-wrapper

.mvn/wrapper/maven-wrapper.properties

maven 3.9.9

Branch release/4.0.x

github-actions

.github/workflows/build.yml

dropwizard/workflows main

dropwizard/workflows main

.github/workflows/release.yml

dropwizard/workflows main

.github/workflows/trigger-release.yml

dropwizard/workflows main

maven

pom.xml

io.dropwizard.modules:module-parent 4.0.2

org.flywaydb:flyway-core 10.17.1

org.flywaydb:flyway-database-postgresql 10.17.1

com.h2database:h2 2.3.232

maven-wrapper

.mvn/wrapper/maven-wrapper.properties

maven 3.9.9

Check this box to trigger a request for Renovate to run again on this repository

dropwizard / dropwizard-flyway Goto Github PK

dropwizard-flyway's Introduction

Dropwizard

Want to contribute to Dropwizard?

Need help or found an issue?

Sponsors

JetBrains

dropwizard-flyway's People

Contributors

Stargazers

Watchers

Forkers

dropwizard-flyway's Issues

Repository problems

Ignored or Blocked

Detected dependencies

Recommend Projects

Recommend Topics

Recommend Org