Thanks Yarick.
For anyone searching the archive, I needed to update the file
junit/runner/excluded.properties in $IDEA_HOME/lib/junit.jar to be the
following:
#
# The list of excluded package paths for the TestCaseClassLoader
#
excluded.0=sun.*
excluded.1=com.sun.*
excluded.2=org.omg.*
excluded.3=javax.*
excluded.4=sunw.*
excluded.5=java.*
excluded.6=org.w3c.dom.*
excluded.7=org.xml.sax.*
excluded.8=net.jini.*
Hope this helps someone.
Cheers,
Dan
-----Original Message-----
From: Yas Sok [mailto:[EMAIL PROTECTED]]
Sent: 22 July 2002 10:42
To: [EMAIL PROTECTED]
Subject: [Eap-bugs] Re: junit linkage error
Hi, Dan.
It is not IDEA bug - it is JUnit feature. JUnit team described it in the
FAQ.
The matter is that in order to reload classes on every run they wrote own
class loader,
which has these features. For detailed descriptions, please, look at the FAQ
on www.junit.org.
To avoid that you can disable class reload feature in GUI test runner config
file
or mark some jars (I do not remember which concrete) as not reloadable.
With the best regards,
Yarick.
North, Dan (Thought Works ) wrote:
> Hi there.
>
> Not really a bug in IDEA, more likely some broken classpath nonsense, but
I
> wonder if anybody can point me in the right direction.
>
> I can run my unit tests perfectly well in IDEA if I use the text runner,
but
> if I use the UI runner, I sometimes come up against a LinkageError as
> follows:
>
> java.lang.LinkageError: loader constraints violated when linking
> org/xml/sax/XMLReader class.
>
> I'm using vanilla xerces and xalan. Is there perhaps something under the
> junit hood that is using a conflicting xml reader? Any help gratefully
> received - I'm much happier looking at a green bar than a row of dots :o)
>
> Cheers,
> Dan
_______________________________________________
Eap-bugs mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-bugs
_______________________________________________
Eap-bugs mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-bugs
