tbroyer/gwt-maven-plugin — pull request #12 by niloc132 (2013-11-10 22:38:55+00:00)
Title: First step in updating to GWT 2.6.0-rc1

Fix for #11 - this gets the compile mojo to pass all integration tests and exposes new features, though still doesn't get `gwt:test` to work correctly. Current stack trace:

[ERROR] Unexpected error while processing XML
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration
at org.apache.xerces.parsers.SAXParser.(Unknown Source)
at org.apache.xerces.parsers.SAXParser.(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.(Unknown Source)
at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source)
at com.google.gwt.dev.util.xml.ReflectiveParser.createNewSaxParser(ReflectiveParser.java:65)
at com.google.gwt.dev.util.xml.ReflectiveParser.access$000(ReflectiveParser.java:46)
at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:343)
at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$200(ReflectiveParser.java:68)
at com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:418)
at com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:333)
at com.google.gwt.dev.cfg.ModuleDefLoader$1.load(ModuleDefLoader.java:100)
at com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:197)

Haven't yet debugged too far, but the ModuleDefLoader and ReflectiveParser don't appear to have changed appreciable. What has changed is the version of xerces used in gwt-dev.jar:

-
-
-
+
+
+

This change was in https://gwt.googlesource.com/gwt/+/8c269b61 with review at https://gwt-review.googlesource.com/#/c/4323/. I'm not sure if we need classpath trickery to make this work, or if this is a version conflict of some sort - I don't see any existing classpath trickery this work though, nor do I see another version on the classpath (aside from the one in java itself, which has a different package, so seems unlikely to be involved.