Now that commons-configuration gets the latest and greates vfs it also
gets the latest of Xalan and we are back to this failure

All errors I checked look like this one

http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_file/TEST-org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader.xml.html

I.e.

java.lang.NoClassDefFoundError: 
org/apache/xml/serializer/OutputPropertiesFactory
        at 
org.apache.xalan.templates.OutputProperties.<init>(OutputProperties.java:83)
        at 
org.apache.xalan.transformer.TransformerIdentityImpl.<init>(TransformerIdentityImpl.java:88)
        at 
org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:823)
        at 
org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader.testParse(TestHierarchicalConfigurationXMLReader.java:56)

My reading of it is that configuration uses an identity transform in
order to serialize XML, the trunk of Xalan uses (Xerces')
serializer.jar to actually implement transformation output and that
serializer.jar is not on the CLASSPATH because the configuration's POM
doesn't list it as a dependency.

I have no idea when Xalan started to use serializer.jar, but there is
a separate serializer artifact available for the groupId xalan - who's
only version available is 2.7.1.  So maybe adding the serializer to
your POM would help.

So far I'd expect the build to fail if you upgraded Xalan to 2.7.1
(and maybe Xerces to 2.9.1) for any build outside of Gump for the same
reasons as well, but then again the serializer change may have occured
after the 2.7.1 release of Xalan.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to