This is a known JUnit issue which is covered on the JUnit web site. Certain jars have special properties for security reasons and if you violate their security requirements then they cause an exception.
Crimson is definitely one of them. In a regular JUnit environement, there is a file that you can use to tell the special JUnit class loader to exclude the packages from those jars. Unfortunately, there is no easy way to modify this file in IDEA. Right now the only straightforward solution is to use the text runner - though I suppose it might be possible to supercede the file by playing with the classpath. On Mon, 6 May 2002, Reto Badertscher wrote: > when performing JUnit test with the graphical UI i get errors, which i don't > get when running in text modes. > For example when using org.apache.commons.logging used in the jakarta poi. > A similar problem i had using JDOM with crimson (with Xerces it's OK). > > Is there something which has to be taken care (classpath) when using the > graphical UI or is it more recommended to work in the text modus. _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
