You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Daniel Kulp (JIRA)" <ji...@codehaus.org> on 2006/03/20 20:35:11 UTC
[jira] Created: (MSUREFIRE-81) In forked modes, many API jars
cannot be used due to problems loading QName class
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
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
[jira] Moved: (SUREFIRE-228) In forked modes, many API jars cannot
be used due to problems loading QName class
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-81 to SUREFIRE-228:
------------------------------------------------
Affects Version/s: (was: 1.5.2 (2.1.2 plugin))
Key: SUREFIRE-228 (was: MSUREFIRE-81)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> In forked modes, many API jars cannot be used due to problems loading QName class
> ---------------------------------------------------------------------------------
>
> Key: SUREFIRE-228
> URL: http://jira.codehaus.org/browse/SUREFIRE-228
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Linux, JDK 1.5.0_06
> Reporter: Daniel Kulp
> Assigned To: 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
[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars
cannot be used due to problems loading QName class
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MSUREFIRE-81) In forked modes, many API jars cannot
be used due to problems loading QName class
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=all ]
Brett Porter closed MSUREFIRE-81:
---------------------------------
Assign To: Brett Porter
Resolution: Won't Fix
Fix Version: (was: 2.2)
you have to use child delegation = false, or include an implementation of the xml parser. Surefire uses a child-first (webapp) classloader by default, and if you provide your own xml apis, then you must provide an implementation
> 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
[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars
cannot be used due to problems loading QName class
Posted by "Daniel Kulp (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=comments#action_61567 ]
Daniel Kulp commented on MSUREFIRE-81:
--------------------------------------
<childDelegation>false</childDelegation> did work.
This should definitely be the default for fork modes. Having tests not pass in fork mode that pass fine in non-fork mode is not a good situation.
> 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
> 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
[jira] Updated: (MSUREFIRE-81) In forked modes, many API jars
cannot be used due to problems loading QName class
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=all ]
Brett Porter updated MSUREFIRE-81:
----------------------------------
Description:
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.
was:
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.
Fix Version: 2.2
> 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
> Priority: Critical
> Fix For: 2.2
>
>
> 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
[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars
cannot be used due to problems loading QName class
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=comments#action_61558 ]
Carlos Sanchez commented on MSUREFIRE-81:
-----------------------------------------
Can you try setting <childDelegation>true</childDelegation> in the
surefire plugin configuration?
> 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
> 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
[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars
cannot be used due to problems loading QName class
Posted by "Daniel Kulp (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=comments#action_61566 ]
Daniel Kulp commented on MSUREFIRE-81:
--------------------------------------
Didn't help at all. Nothing changed.
> 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
> 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