[mojo-dev] [jira] (MCOBERTURA-179) JAXB and XmlParser settings not properly copied?

Mon, 23 Sep 2013 06:17:57 -0700

Issue Type: Bug Bug
Affects Versions: 2.6
Assignee: Unassigned
Created: 23/Sep/13 8:16 AM
Description:

When upgrading to JDK 7, I encounter a rather strange behaviour which seems to indicate that Cobertura's forked runner execution has a classpath which differs from the classpath of the original surefire plugin. That is:

a) When running mvn clean package, all [unit] tests pass.
b) When running mvn cobertura:check in the same project the unit tests blow up with the following, rather interesting, exception:

org.xml.sax.SAXNotRecognizedException: Feature 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
	at com.sun.xml.bind.v2.util.XmlFactory.createParserFactory(XmlFactory.java:128)
	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.getXMLReader(UnmarshallerImpl.java:154)
	at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:157)
	at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:214)
	at se.jguru.nazgul.core.xmlbinding.spi.jaxb.JaxbXmlBinder.unmarshal(JaxbXmlBinder.java:169)



The secure-processing parameter is mandatory for ParserFactory implementations since quite awhile back - and since the ParserFactory used in the normal surefire-plugin execution works well, I'm assuming that the cobertura plugin misses to transfer some XML ParserFactory (default) setting from the standard lifecycle into its execution.
Project: Mojo's Cobertura Maven Plugin
Priority: Major Major
Reporter: Lennart Jörelid
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to