2.0RC2 Test Changelogs using wrong schema

Liquibase Development
1

Hello guys,

Just had a quick read through the liquibase build logs over at ops4j.org and saw this:

    build 06-Jan-2010 01:58:07 ------------------------------------------------------- build 06-Jan-2010 01:58:07 T E S T S build 06-Jan-2010 01:58:07 ------------------------------------------------------- build 06-Jan-2010 01:58:07 Running liquibase.integration.commandline.MainTest build 06-Jan-2010 01:58:07 LiquiBase Version: 2.0-rc2-SNAPSHOT build 06-Jan-2010 01:58:07 build 06-Jan-2010 01:58:07 Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.439 sec build 06-Jan-2010 01:58:07 Running liquibase.integration.commandline.CommandLineFileOpenerTest build 06-Jan-2010 01:58:07 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec build 06-Jan-2010 01:58:07 Running liquibase.executor.JdbcExecutorTest build 06-Jan-2010 01:58:08 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.889 sec build 06-Jan-2010 01:58:08 Running liquibase.parser.core.xml.XMLChangeLogSAXParserTest build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/simpleChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/multiChangeSetChangeLog.xml is using schema version 1.9 rather than version 2.0 build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/logicalPathChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/preconditionsChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/nestedChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/simpleChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:09 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/nestedRelativeChangeLog.xml is using schema version 1.9 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/simpleChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/doubleNestedChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/nestedChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/simpleChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/doubleNestedRelativeChangeLog.xml is using schema version 1.9 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/nestedRelativeChangeLog.xml is using schema version 1.9 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/simpleChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:10 INFO 1/6/10 1:58 AM:liquibase: liquibase/parser/core/xml/malformedChangeLog.xml is using schema version 1.4 rather than version 2.0 build 06-Jan-2010 01:58:10 SEVERE 1/6/10 1:58 AM:liquibase: cvc-complex-type.2.4.a: Invalid content was found starting with element 'unknownTag'. One of '{"http://www.liquibase.org/xml/ns/dbchangelog/1.4":comment, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":createTable, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropTable, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":createView, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":renameView, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropView, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":insert, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addColumn, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":sql, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":createProcedure, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":sqlFile, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":renameTable, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":renameColumn, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropColumn, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":modifyColumn, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":mergeColumns, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":createSequence, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":alterSequence, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropSequence, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":createIndex, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropIndex, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addNotNullConstraint, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropNotNullConstraint, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addForeignKeyConstraint, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropForeignKeyConstraint, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addPrimaryKey, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropPrimaryKey, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addLookupTable, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addAutoIncrement, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addDefaultValue, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropDefaultValue, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":addUniqueConstraint, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":dropUniqueConstraint, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":customChange, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":executeCommand, "http://www.liquibase.org/xml/ns/dbchangelog/1.4":rollback}' is expected. build 06-Jan-2010 01:58:10 Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.047 sec

Seems like its still using the 1.4 schema definition instead of the 2.0 definition. Should that test not fail?

Regards,
—Jaco

2

There is no problem with running liquibase against an older schema.  Anything valid in a previous 1.x version is fully compatibly with later versions.  You just won’t be able to use newer tags until you update your schema reference.  The warning is simply a message pointing out the problem so you don’t spend too long wondering why you can’t use new tags.

Nathan