Incompatibility with jdk1.6.0_18 and higher?

General Discussion
1

We’re seeing the following error when running Liquibase programs against JDKs with revisions of 1.6.0_18 and higher. It appears that those newer JDKs have made an XML-parsing API stricter, and that Liquibase (version 1.9.5) fails against that stricter API. Is there a Liquibase release that avoids this problem? Or do we need to stay with lower-numbered JDKs for a while? Or am I barking up the wrong tree?

===============================

[java] liquibase.exception.MigrationFailedException: Migration failed for change set foo.changelog.xml::bar::foobar:
    [java]      Reason: liquibase.exception.UnsupportedChangeException: liquibase.exception.CustomChangeException: java.lang.IllegalStateException: Method getLocalName() cannot be called for CHARACTERS event.:
    [java]          Caused By: liquibase.exception.CustomChangeException: java.lang.IllegalStateException: Method getLocalName() cannot be called for CHARACTERS event.:
    [java]          Caused By: java.lang.IllegalStateException: Method getLocalName() cannot be called for CHARACTERS event.:
    [java]          Caused By: Method getLocalName() cannot be called for CHARACTERS event.
    [java]    at liquibase.ChangeSet.execute(ChangeSet.java:260)
    [java]    at liquibase.parser.visitor.UpdateVisitor.visit(UpdateVisitor.java:26)
    [java]    at liquibase.parser.ChangeLogIterator.run(ChangeLogIterator.java:41)
    [java]    at liquibase.Liquibase.update(Liquibase.java:112)
    [java]    at liquibase.Liquibase.update(Liquibase.java:136)

=======================================

Are others seeing this error? I’ve searched the web, the Liquibase site, and the forum archives, and come up empty, so please forgive me if this has already been discussed.

Thanks for any help,

    Andy Cohen

2

At least current 2.0 trunk release works correctly with that version.

3

Good, that was just what I was going to ask.  It’s not an error I’d seen before on 1.9, but I may not have tested it on that new of a 1.6 release.

Nathan

4

Is there any plan to fix this bug in 1.9? If not, when do you expect 2.0 to be ready for prime time?

Thanks for all your work,

   Andy Cohen

5

My hope is to get another RC of 2.0 out next week.  I seem to keep promising that, though…

As for a fix for 1.9, I’ll have to do more research into what is causing the problem.  I will probably not be able to look into it until I can get the 2.0 RC out, though.  If it is something straightforward to fix, I will fix it in 1.9 since I plan to support that branch going forward as well.

Nathan