# HG changeset patch # User Oleksandr Gavenko # Date 1450694438 -7200 # Node ID 031c61d1a8bd1acef6d8ce582c387ff76854eb2c # Parent 422610dafebec09134f6de69d0ffb6842c4cbc56 Introducing LiquiBase to existing project. diff -r 422610dafebe -r 031c61d1a8bd liquibase.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/liquibase.rst Mon Dec 21 12:40:38 2015 +0200 @@ -0,0 +1,54 @@ +.. -*- coding: utf-8; -*- +.. include:: HEADER.rst + +============ + LiquiBase. +============ +.. contents:: + +Introducing LiquiBase to existing project. +========================================== + +Official statement about introducing LiquiBase to existing project are: + + http://www.liquibase.org/documentation/existing_project.html + Adding Liquibase on an Existing project + +There are two approaches: + + * create full schema definition prior to introducing Liquibase + * works only with current changes becase Liquibase basically work only with changesets and only + special supplied instruments care about full schema definition + +To create full schema debinition you may run:: + + mvn liquibase:generateChangeLog -Dliquibase.outputChangeLogFile=... + +on clean project without Liquibase. Or set name for changelog output file in ``pom.xml``. +(here reduced not fully worked declaration):: + + + org.liquibase + liquibase-maven-plugin + ${liquibase.version} + + changelog.xml + + + +.. NOTE:: + + ``pom.xml`` settings have precedence over ``-Dliquibase.outputChangeLogFile=...`` unless you + define it as:: + + + ${project.build.directory}/changelog.xml + + + + + ${liquibase.outputChangeLogFile} + + + +