Yep, we did it.
Our current changelog is composed of a root xml containing tags for several other changelogs reaching some tenths of megabytes. Running Liquibase 1.8.1 Ant task, using Eclipse 3.3.2, Ant 1.7.0 and JDK 1.6.0_03, results in the following error:... [migrateDatabase] Reading from DATABASECHANGELOG [migrateDatabase] Release Database Lock [migrateDatabase] Successfully released change log lock
C:\Dados\workspace-europa\DmView-Enterprise-HEAD\data\build.xml:326: java.lang.OutOfMemoryError: Java heap space
It runs fine when I increase the JVM memory with “-Xmx128m”. My only question/suggestion here is: would it be possible to improve Liquibase memory management? Loading the changelog on demand, for example.