[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars cannot be used due to problems loading QName class

2006-03-20 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=comments#action_61558 ] Carlos Sanchez commented on MSUREFIRE-81: - Can you try setting true in the surefire plugin configuration? > In forked modes, many API jars cannot be used due to problems load

[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars cannot be used due to problems loading QName class

2006-03-20 Thread Daniel Kulp (JIRA)
[ 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 > -

[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars cannot be used due to problems loading QName class

2006-03-20 Thread Daniel Kulp (JIRA)
[ http://jira.codehaus.org/browse/MSUREFIRE-81?page=comments#action_61567 ] Daniel Kulp commented on MSUREFIRE-81: -- false did work. This should definitely be the default for fork modes.Having tests not pass in fork mode that pass fine in non-

[jira] Commented: (MSUREFIRE-81) In forked modes, many API jars cannot be used due to problems loading QName class

2006-05-01 Thread Brett Porter (JIRA)
[ 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 m