Liquibase

2.0.5 has been released. This is to fix a couple regressions introduced in 2.0.4.

Download from http://liquibase.org/download

Bug Fixes:

• Removed new load blob/clob data from files feature
• Fixed linux distribution shell script
• Command line updateSQL output is once again going to STDOUT

Full release notes: https://liquibase.jira.com/secure/ReleaseNote.jspa?projectId=10020&version=10360

2.0.4 has been released. This is primarily a bug fix release during the main development on 3.0, but does include a few  enhancements as well.

Download from http://liquibase.org/download

New features:

• LoadUpdate support for H2
• Support ${} params in sql files
• Ability to load blob/clob data from files

Full release notes: https://liquibase.jira.com/secure/ReleaseNote.jspa?projectId=10020&version=10160

Since 3.0 is taking longer than I was hoping , it may make sense to have a 2.0.4 release with high value/easy fixes for those waiting for specific problems.

Are there existing bugs in http://liquibase.jira.com or pull requests at http://github.com/liquibase that you would like to see in a 2.0.4 release?

Preference will be given to bugs/features that have patches that can simply be applied to the 2.0 branch, since I don’t want to take more time away from 3.0 than I have to.

It has been a while since the last Liquibase release, and I wanted to give a quick status update.

The main thing I have been working on is the next version of Liquibase, which I am going to call 3.0.0. For those of you following along, the goal of 2.0 was to create an extensible system on top of liquibase as well as solidify the liquibase APIs for anyone wanting to integrate liquibase into their applications. Due to the size of that undertaking, the “diff” support did not get the same API cleanup and extensibility system in the 2.x release.

For the last several months I have been going through the diff side of the codebase, adding things such as:

• Standardized ways to specify mappings between “standard types” and “database specific types” in changeslogs
• Support for differentiation between catalogs and schemas
• The ability to add custom database objects to extract and compare in the snapshot/diff process
• The ability to change how database objects are extracted and compared
• Support for annotations in defining Change classes to make for easier subclassing
• Support for custom diff reporting formats
• Ability to handle multiple cross schema and catalog references in diffs

All-in-all I have about 400 changed files in my local repository that I have been waiting to push up to github until it is in a coherent state. I keep thinking “I’m sure it will be ready by next week” but keep finding more I would like to get done first. Because my local repository is so different than the github repository, I have not been bringing in the pull requests as I normally would. I will get to those once I get my changes pushed since I tend to do some modifications to the commits as part of the integration process.

I am calling the next version 3.0 rather than 2.1 because of the potentially breaking changes between 2.0 and 3.0. From an end-user standpoint, there will be little to no changes in the changelog format. Most breaking changes are in the internal liquibase APIs for those integrating liquibase and/or writing extensions. More information will be made available on breaking changes closer to release date.

Besides the code, I spent time lately dealing with defacement issues on liquibase.org and blog.liquibase.org. Because of this attack and earlier spam scripts that abused the wiki system, I am going to move the documentation and site from the current dokuwiki system to github. This has the advantage of better performance, the ability to manage branches of the documentation, and the ability to include an offline version of the manual with each release. Documentation changes will require a github pull request rather than the simpler wiki-style direct editing, however.

My planned timeline for 3.0 is to commit what I have within the next week or so, then merge in the pull requests and create a “3.0 alpha 1″ release. I moved around a lot of database-specific code that will take a while for me to test and would like to get some feedback from the community as soon as possible on new bugs or regressions that were introduced by the changes. I will make an announcement when the first 3.0 release is available for testing.

2.0.3 is a very small update, mainly fixing the maven repository and the end of line char in the command line unix shell script.

Other bugs fixed are:

• Allow Changelog Parameters in raw SQL changesets and formatted SQL changelogs
• Sybase NUMERIC issue
• An issue with DB2 and defaultSchema

Liquibase 2.0.2 has been released. It is primarily a bugfix release on the 2.0.1 release and can be downloaded from http://liquibase.org/download.

Visit the forum with any comments or questions. Release notes are available from liquibase.jira.com

With the 2.0.2 release, main development will shift to the 2.1 release. Liquibase 2.1 planning has begun with this forum post

I am planning a Liquibase Online Meetup for July 28th, 2011 at 12:00 US Central Time (GMT-5).

For more information, see http://forum.liquibase.org/#Topic/49382000000252083

For those of you watching and/or contributing to the Liquibase source code, the repository has now moved from the old subversion repository at liquibase.jira.com to http://github.com/liquibase/liquibase.

Liquibase extensions maintained by the main Liquibase team have also been moved to the liquibase github group at http://github.com/liquibase.

If you have any questions, feel free to ask on the Liquibase development forum

For NetBeans users, there is a Liquibase plugin now available.

The current, 0.2 version implements rudimentary support and concentrates on the most needed functionality.

Features:

• Database connections stored in the Database Explorer plugin, so the developer doesn’t have to separately maintain the registry of connections.
• Executing a changeset by simply selecting it in the File or Project explorer windows and call the execution from a context menu action. The database connection can be selected during the execution
• A formatted log is displayed in the Output Window about the execution of the changeset, so the developer is properly informed if the changeset execution has failed.
• Custom icon for the Liquibase changeset files, so they can better distinguished from the ordinary files.

More information: http://plugins.netbeans.org/plugin/38564/liquorice-core

Kumar Shantanu has implemented a Clojure DSL/wrapper for Liquibase which is has reached version 0.1. It is available at https://bitbucket.org/kumarshantanu/clj-liquibase/src. One more option for all you XML-haters out there

Nathan