This fork of Liquibase is oriented towards requirements The Kuali Foundation has for database migration tooling. This version is a superset of the original Liqubase functionality. It contains every commit from the parent GitHub repository (since the time of the fork) in addition to Kuali oriented features.
One requirement for Kuali is that applications need to be database agnostic. Towards this end, Kuali applications adhere to a subset of database functionality that is present across Oracle, MySQL, and embedded databases (H2, Derby, etc).
This page documents the desired workflow for Kuali database tooling along with features/extensions/modifications that have gone in.
Altered POM's:
- Top level pom inherits from the Kuali pom
- groupId's changed to org.kuali.*
- Stripped out quite a bit of configuration that was redundant or otherwise not needed
- Changed the <scm> section to reflect the location of the source on GitHub
- All of the java based artifacts get deployed, including the example code
The built in Maven lifecyles (clean, site, and default) work
The Maven Release plugin works
Source has been cleaned up by:
- Applying uniform code formatting
- Organizing / sorting import statements
- Removing .* import statements
- A few other whitespace/formatting touch ups