In my last blog, I showed you how to configure Liquibase using Maven. The last step for using Liquibase in a modern development environment is to configure it using Spring.
First you need to configure your Maven pom.xml to get all the dependency classes for the Spring bean. Here is a sample configuration:


Next, you will need to configure your datasource. There are several ways to do this. Here is an example of one:

<jee:jndi-lookup id="mySqlDataSource" jndi-name="java:comp/env/jdbc/mysqlData"/>

Finally, you will need to configure your Spring bean in your applicationContext.xml file. Using my example from the previous blog, here is a sample of what your bean configuration should look like:

<bean id="liquibaseBean" class="liquibase.integration.spring.SpringLiquibase">
      <property name="dataSource" ref="mySqlDataSource" />
      <property name="changeLog" value="classpath:changelog-base.xml" />

That is it! The spring configuration is set in your application. Now when you deploy your application, the application will load the change file into the database and continue starting your application. Your application will always have the correct data loaded when the application is started. If you have multiple branches with multiple test sets of data, this makes the process much easier.
I hope that these blogs have peaked your curiosity about Liquibase. There are many features that I did not mention that need more exploring. Hopefully these blogs will inspire to look into Liquibase as a solution to your development needs.