You should now be able to run your unit tests again as it's put all the classes within the sub-modules encapsulated by the top-level POM on the classpath. Tick the 'Include Modules' box, click 'Apply', agree to Maven possibly trashing your project and wait.

Right-click on the project in the left-hand pane and choose 'Properties' then click 'Maven' and you should be presented with the screen below: classpath files before you perform the steps below.Īfter much web searching to no avail and then much headscratching I finally found the solution tucked away in the project's Maven settings. The Maven project in question has the Java source and unit test classes in sub-modules and the Maven plugin wasn't adding these sub-modules to the classpath. It intercepts the fork operation so that it can correctly build the classpath with all the appropriate dependencies, the only thing that was missing on the classpath was any reference to the project's Java class files! It is fails with a 'ClassNotFoundException ' then you have this problem.Īfter obtaining the classpath that Eclipse was using to spawn off the unit test it was clear that Maven (or more correctly the Maven m2eclipse plugin) was the root of the issue. To see if you have this problem open any unit test within Eclipse and then run it as a JUnit test (or just CTRL-F11). I've never had any problems running unit tests within Eclipse until recently after I update the plugin. I've been using Eclipse & Maven for a while now and have the m2eclipse plugin installed so that Eclipse understands the Maven dependencies.

Install junit in eclipse