On 6/8/07, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
Snippet of the "mvn test -X" ouput: ================================== <snip> [DEBUG] Test Classpath : [DEBUG] K:\Sources\Prefs\memoryprefs\target\test-classes [DEBUG] K:\Sources\Prefs\memoryprefs\target\classes [DEBUG] K:\Sources\Prefs\memoryprefs\target\classes [DEBUG] K:\Sources\Prefs\memoryprefs\target\test-classes [DEBUG] K:\Repositories\maven2\.m2\repository\junit\junit\4.3.1\junit-4.3.1.jar [DEBUG] K:\Repositories\maven2\.m2\repository\org\slf4j\slf4j-simple\1.4.0\slf4j -simple-1.4.0.jar [DEBUG] K:\Repositories\maven2\.m2\repository\org\slf4j\slf4j-api\1.4.0\slf4j-ap i-1.4.0.jar <snap>
Hi Minto I have reduced your output to show nothing but the test classpath that is defined by your project. As you can see, both target/classes and target/test-classes are included. (Twice, it seems.. kind of strange..) Also your dependencies are listed. The only stuff that is appended by Eclipse are the eclipse jars.. Note that compilation and running tests in Eclipse is done by Eclipse itself, not by Maven. If your custom classloader uses the system classloader for delegation, there is no way to catch the additional libararies. Since the sourceode of the classloader is already in your project, you might as well adjust it. Try using the context classloader as a parent instead. Cheers Jo
