Liquibase

Beta 1 of LiquiBase 2.0 has been released.  It can be downloaded from http://www.liquibase.org/download.

The main improvement over milestone 1 is that it can be ran against existing changelog scripts, so it can be fully tested with existing databases.

Also, do not forget the LiquiBase Extension Contest currently underway!

LiquiBase 2.0 is all about 3rd party extension and integration, and to help kick that off, we are holding a contest.

Thanks to donations from Atlassian and O’Reilly, we have some great prizes for the winners

Rules

• Your entry must embed or extend LiquiBase
• Extensions must be compatible with Liquibase 2.0 (currently under construction)
• Your plugin must be listed on the LiquiBase Extension Portal
• You must announce your extension and your interest in submitting it to this contest on the LiquiBase User Forum
• There is no license restrictions on your plugin, although we prefer an open source license

Prizes
Grand Prize:

• Your choice of 5 O’Reilly books, donated by O’Reilly
• One copy of PostgreSQL

Runner Up:

• Atlassian laptop bag from Timbuk2 (US$150 value), donated by Atlassian
• One copy of MySQL Community Edition

5x Honorable Mentions:

• Your choice of 1 O’Reilly book, donated by O’Reilly
• One copy of JavaDB

Judging

The winning plugins will be judged by lead developer Nathan Voxland on:

• Usefulness
• Creativity and Elegance
• Completeness
• Code quality and documentation

Key Dates

• June 24th, 2009: Contest opens
• August 31st, 2009, High Noon, US Central Time (GMT-5): Contest closes
• September 15th, 2009: Winners Announced

For more information, see the offical contest page

The first public release of LiquiBase 2.0 is now available.  This release is a milestone release, and therefore not for general consumption, it is not even at beta stage yet.

The focus of milestone 1 was a major refactoring and standardization of the external-facing APIs to give 3rd party extension contributors a stable platform to build on.  We have not yet begun to address bugs found in 1.9 or implement new functionality.  Additionally, the checkum generation logic has changed and is currently incompatible with checksums generated in liqubase 1.x.  LiquiBase 2.0 final will handle upgrades graceful.

Because it is just a milestone release, the download packages are not on sourceforge, but are linked from the download page.

Please let us know of any feedback, questions, or bugs you find.   Although we have focused on stabilizing the API, parts may change during the milestone phase based on feedback from the community.

The roadmap for 2.0 is to have several milestone releases, followed by a beta period.  2.0 final is scheduled for a September release, although that may change.

Note: Don’t forget the LiquiBase online meetup tomorrow!

LiquiBase 1.9.4 has been released.  The 1.9.x branch continue to be maintained, even as work continues on LiquiBase 2.0.

1.9.4 is primarily a bug fix release, but also introduces the following features:

• DB2 for iSeries support
• Improved Maven support
• executeCommand does not run under updateSQL etc.

As usual, you can download the newest version from http://www.liquibase.org/download and post any questions or issues to http://www.liquibase.org/forum

We would like to thank Mark Logemann, Don Smith, and Oleg Taranenko for the patches they submitted.

We will be having our first meetup 2009-6-25 at 12:00 PM US central time (GMT-5) using the “Chat” functionality of the LiquiBase community forum (http://liquibase.org/forum/chat/index.php).  To log in, you will need to be registered on http://www.liquibase.org/forum/

I will be there to discuss the upcoming 2.0 release, development processes, outstanding issues and feature requests, and anything else of interest to participants.  Planned time is 1 hour.

Hope to see you there

Thanks to the generous people at Atlassian, we now have a much nicer issue tracker and source browser than before. You can check out our Jira instance at http://liquibase.jira.com/browse/CORE and our svn repository at http://liquibase.jira.com/source/browse/CORE.

The issues were bulk moved from the sourceforge tracker, so I will be going over them to recategorize and prioritize them over the next week.

We also now have a message board at http://www.liquibase.org/forum in place of the old liquibase-user, liquibase-devel, and liquibase-doc mailing lists. A copy of all top-level (non-reply) posts are being forwarded to the mailing lists to help with the transition, but please use the forum from now on.

If you have any comments or suggestions on the new setup, please let me know.

LiquiBase 1.9.2 has been released.  It is a bugfix release, mainly around issues with the includeAll tag.

Like always, it can be downloaded from http://www.liquibase.org/download

LiquiBase 1.9.1 has been released which addresses several bugs.  Most bugs were relatively minor, but it is recommended you upgrade.

Some of the bugs fixed include:

• H2 schema capitalization issues
• Improved “local database” detection
• Improved database snapshot generation for Oracle and MSSQL
• Bug fixes in Sybase AS Anywhere support
• Handle urls with an authority component when using includeAll
• Fixed bug with “runInTransaction” attribute
• Support for Grails 1.1-SNAPSHOT
• Escape hsql tables/columns that are keywords

As usual, visit http://www.liquibase.org/download to download the update.

LiquiBase 1.9.0 has been released!

Major features include:

• <modifySql> support
• <includeAll> support
• Sybase Adaptive SQL Anywhere support
• Paths in <include> can be relative to changelog using the “relativeToChangeLog” attribute
• <stop> support
  
• runInTransaction attribute for changeSet
• Stronger validation in .xsd
• Better Derby support (drop column, rename column)
• Bug fixes

If you are using the standard LiquiBase library, upgrading is simply a matter of replacing the liquibase.jar file.   If you are using Grails, Maven, or the IntelliJ plugin, an updated version should be available via standard plugin repository within in the next day.

NOTE: DUE TO A BUG IN THE “ADD NOT NULL CONSTRAINT” AND “DROP NOT NULL CONSTRAINT” CODE, YOU WILL GET CHECKSUM VALIDATION ERRORS FOR EXISTING CHANGESETS THAT USE THOSE TAGS.

To solve the problem, either:

1. Add the <validCheckSum> tag to the failing changesets specifying the old MD5 sum (the one listed in the validation failed message)
2. Or, run “UPDATE DATABASECHANGELOG SET MD5SUM=NULL”

To take advantage of newer change log features, change your XSD declaration to:

<databasechangelog xmlns=”http://www.liquibase.org/xml/ns/dbchangelog/1.9″
xsi=”http://www.w3.org/2001/XMLSchema-instance”
schemalocation=”http://www.liquibase.org/xml/ns/dbchangelog/1.9
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd”>

Download LiquiBase 1.9 from:

http://www.liquibase.org/download

As usual, make sure you let us know if you have any questions, problems, or ideas.  Also, thank you to everyone who submitted bug reports and patches over the last couple months.

LiquiBase 1.8.1 is now available for download.  It is a bug fix release that fixes several minor bugs found in 1.8.0.

As usual, if you have any questions or comments, please let us know.