Share your experience with Database DevOps by taking part in the 2021 State of Database DevOps survey Take the survey

Flyway 3.2 Released

The Flyway 3.x series started just under a year ago. And what a ride it's been!

So without further ado, please welcome Flyway 3.2! The hightlights of this release are:

  • Many improvements to the command-line tool
  • solidDB support
  • Improved JavaBean-style configuration
  • Follow blog by email

Many improvements to the command-line tool

The first and most important one is that Flyway Command-line now ships with a JRE

Flyway Command-line

Why is this important? With the bundled JDBC drivers added in Flyway 3.1 and now the Java Runtime Environment, Flyway Command-line now has zero required external dependencies. All you need to do to get started is unpack the distribution, configure your database connection, add your first SQL migration files and off you go. Getting started has never been easier!

The other improvement we made is the ability to easily share an installation. Flyway will now by default also look for a flyway.conf file in the current directory. And all relative paths are now relative to the current directory as well. This is great for server environments, where one read-only installation of the Flyway Command-line distribution can then be shared by many projects.

Last but not least, we also added a -q switch to only output errors and warnings.

solidDB support

Building upon the ever growing list of supported databases, this release adds official support for solidDB:


Special thanks to Michael Forstner for contributing this!

Improved JavaBean-style configuration

On projects working with Spring's XML configuration, JavaBean-style property access is the way to go. In the past, Flyway has overloaded a number of accessors, making this harder than it should have been. This has now been fixed. As of Flyway 3.2, all properties are configurable using JavaBean-style accessors as used by Spring XML. As usual, Flyway makes things easy and the old methods have first been deprecated to ensure a smooth migration path. They will only be removed in 4.0

<bean id="flyway" class="org.flywaydb.core.Flyway" init-method="migrate">
    <property name="dataSource" ref="..."/>
    <property name="baselineVersion" value="..."/>
    <property name="baselineVersionAsString" value="..."/>

Special thanks to David Harrigan for sponsoring the development of this feature!

Follow blog by email

To make it even easier for you to stay updated, we have added the option for you to follow to this blog by email. All you need to do is enter you email address in the field below and you'll never miss an update again. Needless to say this is strictly no spam and you can unsubscribe at any time.

Subscribe by email

Grab it while it's hot!

This release packs in many more small improvements and bug fixes across the board.

Enjoy the release and grab it while it's hot!

All users are encouraged to upgrade.

Spread the word on Twitter and follow @flywaydb to stay in touch.

« Hangout: Database Migrations in Java EE using Flyway
Gradle Plugin Portal »

Recent posts