14 karma · joined February 20, 2010
I was originally quite bullish on FlywayDB until I started looking into Liquibase by way of Dropwizard. I'm personally not quite convinced of the need for native SQL scripting for schema management, as I often like to work in H2 for dev and something else for production.
However, if you primarily want to use JDBC + native SQL to manage your schema, Flyway is quite powerful and easy to fold into your build process.
If 50% of my traffic already tried offering me a client cert the decision to allow them would be an easy one to make.
I do wonder if Maven 3's flexibility will hurt it or help it in the long run. Yes pom.xml is XML, but at least there is only one dialect. If team A likes XML and team B likes Groovy, development manager C will have a fun time getting them to work together on project D.
There already exist link element relationships for next and previous, a user agent need only keep track of those and render the URI bar accordingly if it was desired.