Hello folks, While this could/should likely be a cobertura-plugin specific conversation, it might be prudent to include the comments and thoughts of us all.
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. I'll open a JIRA, but wanted to get your insights first. Is this a known problem with a simple (but undocumented) solution? -- +==============================+ | Bästa hälsningar, | [sw. "Best regards"] | | Lennart Jörelid | EAI Architect & Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype): jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==============================+
