[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=comments#action_64496 ]
Brett Porter commented on MSUREFIRE-81: --------------------------------------- actually, this was resolved by fixing MSUREFIRE-74 - it was a problem of a class appearing in two different classloaders > In forked modes, many API jars cannot be used due to problems loading QName > class > --------------------------------------------------------------------------------- > > Key: MSUREFIRE-81 > URL: http://jira.codehaus.org/browse/MSUREFIRE-81 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.1.2 > Environment: Linux, JDK 1.5.0_06 > Reporter: Daniel Kulp > Assignee: Brett Porter > Priority: Critical > > > JDK 1.5.0 includes the javax.xml.QName class. However, a lot of jars (like > stax-api, various xml jars, axis, etc...) also contain the class. In > non-fork mode, everything works find and referencing a QName object loads the > JDK provided one. In fork mode, you end up with errors like: > java.lang.LinkageError: loader constraints violated when linking > javax/xml/namespace/QName class > or java.lang.NoClassDefFoundError when loading the QName. This makes it > nearly impossible to test various XML related technologies with JDK 1.5.0 in > fork mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
