Re: Running junit test with maven
Hi java.lang.NoClassDefFoundError It might be because the MANIFEST.MF in your jar file is wrong. When you make a pom.xml with a large description clause in the pom the MANIFEST.MF becomes huge. Bigger than allowed for execution. Try to verify the size of the MANIFEST in your jars. /Anders Kr. Andersen Tom Huybrechts wrote: You could also produce a test-jar from the tests from A and include them as test-scope dependency to B. See http://maven.apache.org/guides/mini/guide-attached-tests.html Tom On 4/19/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You need a third module that will contain your share test classes (under src/main/java) and you'll add it as a dependency of module a and b with test scope. Emmanuel Patrick GIRY a écrit : I have defined two module A and B with a common parent module because B depend on A. I have imported the module as Eclipse project. The problem i have a TestCase class into the B module which extends a TestCase into the A module. When I run the test suite with the Eclipse console all is ok, but when I run the mvn test command into the B module, I have java.lang.NoClassDefFoundError with TestCase into A. How can I indicate to surefire plugin to include depend test classpath into it's classpath, to avoid to duplicate the TestCase into the A module? - 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]
Running junit test with maven
I have defined two module A and B with a common parent module because B depend on A. I have imported the module as Eclipse project. The problem i have a TestCase class into the B module which extends a TestCase into the A module. When I run the test suite with the Eclipse console all is ok, but when I run the mvn test command into the B module, I have java.lang.NoClassDefFoundError with TestCase into A. How can I indicate to surefire plugin to include depend test classpath into it's classpath, to avoid to duplicate the TestCase into the A module?
Re: Running junit test with maven
You need a third module that will contain your share test classes (under src/main/java) and you'll add it as a dependency of module a and b with test scope. Emmanuel Patrick GIRY a écrit : I have defined two module A and B with a common parent module because B depend on A. I have imported the module as Eclipse project. The problem i have a TestCase class into the B module which extends a TestCase into the A module. When I run the test suite with the Eclipse console all is ok, but when I run the mvn test command into the B module, I have java.lang.NoClassDefFoundError with TestCase into A. How can I indicate to surefire plugin to include depend test classpath into it's classpath, to avoid to duplicate the TestCase into the A module? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running junit test with maven
You could also produce a test-jar from the tests from A and include them as test-scope dependency to B. See http://maven.apache.org/guides/mini/guide-attached-tests.html Tom On 4/19/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You need a third module that will contain your share test classes (under src/main/java) and you'll add it as a dependency of module a and b with test scope. Emmanuel Patrick GIRY a écrit : I have defined two module A and B with a common parent module because B depend on A. I have imported the module as Eclipse project. The problem i have a TestCase class into the B module which extends a TestCase into the A module. When I run the test suite with the Eclipse console all is ok, but when I run the mvn test command into the B module, I have java.lang.NoClassDefFoundError with TestCase into A. How can I indicate to surefire plugin to include depend test classpath into it's classpath, to avoid to duplicate the TestCase into the A module? - 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]
How to resolve depencies from jar files to .so files with maven? (Interesting problem using SWT jar files that needs dynamic libs and running JUnit test via maven)
Hi, I am building an SWT application. This requires a set of external jar files for SWT and a set of .so shared libraries. The interesting thing is that all code nicely builds via maven and that the test are hanging. By setting maven.junit.fork to false, which I actually should not do since I use a version 1.4 java compiler, I found out that the SWT stuff is going wrong. I added the swt jars to the maven repository and that changes the error I get, but the result is the same. The tests remain hanging. What should I do to make this work? Should I copy the .so files in the same directory as the swt jar files? Or is there another way to indicate these type of dependencies? Any ideas? Regards, Ruud Wijnands
