Antw: LinkageError in Surefire-Plugin in spite of forking
Hello, sorry, I forgot to mention, that I work with Maven 2.0.2. I'm still searching for the reason of the issue with the surefire plugin. I use the latest version of the plugin and checked, that the configuration in the projects pom is really recognized (by using skiptrue/skip I saw, that the test were really skipped). But still playing with the forkMode and childDelegation options doesn't help to get the tests running. I still get 'java.lang.LinkageError: loader constraints violated when linking org/xml/sax/InputSource class'. Is there anyone, who can help? Thanks, Stefan [EMAIL PROTECTED] 06.02.2006 16:57:29 Hello, I have some JUnit tests, that fail with a LinkageError: loader constraints violated when linking org/xml/sax/Parser class. As described in the documentation and other threads in the mailing list, I set forking to once, in order to run the tests in a separate JVM. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode /configuration /plugin Unfortunately this doesn't change anything, I still have the same error. Do you have any other suggestions, what the origin of the problem could be? Thanks a lot for your help! regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: LinkageError in Surefire-Plugin in spite of forking
Hello, I solved the problem. As far as I know, in the latest version the surefire plugin has forking as a default setting. In my pom I still configured the plugin explicitly, as mentioned below. For some reason, the explicit setting of forkModeonce/forkMode leads to an error, during the test execution. Bye, Stefan [EMAIL PROTECTED] 09.02.2006 09:44:19 Hello, sorry, I forgot to mention, that I work with Maven 2.0.2. I'm still searching for the reason of the issue with the surefire plugin. I use the latest version of the plugin and checked, that the configuration in the projects pom is really recognized (by using skiptrue/skip I saw, that the test were really skipped). But still playing with the forkMode and childDelegation options doesn't help to get the tests running. I still get 'java.lang.LinkageError: loader constraints violated when linking org/xml/sax/InputSource class'. Is there anyone, who can help? Thanks, Stefan [EMAIL PROTECTED] 06.02.2006 16:57:29 Hello, I have some JUnit tests, that fail with a LinkageError: loader constraints violated when linking org/xml/sax/Parser class. As described in the documentation and other threads in the mailing list, I set forking to once, in order to run the tests in a separate JVM. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode /configuration /plugin Unfortunately this doesn't change anything, I still have the same error. Do you have any other suggestions, what the origin of the problem could be? Thanks a lot for your help! regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LinkageError in Surefire-Plugin in spite of forking
Hello, I have some JUnit tests, that fail with a LinkageError: loader constraints violated when linking org/xml/sax/Parser class. As described in the documentation and other threads in the mailing list, I set forking to once, in order to run the tests in a separate JVM. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode /configuration /plugin Unfortunately this doesn't change anything, I still have the same error. Do you have any other suggestions, what the origin of the problem could be? Thanks a lot for your help! regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
