Classpath Problems with Maven (m2e-Plugin)

[lweller]

We're using Maven in our projects with m2e plugin. Unfortuately this leads in several classpath issues:

• Libs are automaticaly handled by m2e for each project but they are not exported so JUnitLoop project does not inherit this third part dependencies.
• JUnitLoop project has a dependency to JUnit Lib which may not be the same Version as used in our project

Beside this problems (which are unfortuantely not allow to use it) JUniLoop is a very interesting concept that would relly help developers to reduce response time and so improve their work.

[mirkoseifert]

I agree. The first problem can probably be solved by extending JUnitLoop to recognize the Maven dependencies. However, we do not use Maven at our company which is why there is little interest to implement this. Nonetheless, feel free to send a patch. The second issue is more complex, because multiple project may use different JUnit versions which causes more problems (see issue #8).

[lweller]

Yes I think that it should be possible to collect Maven dependencies to build the classpath. But the problem of differet dependencies per project is even more important with Maven, as just building a classpath with the sum of all dependencies definitly will result in some trouble, as it's really not the Maven way to go.

Personally I think that some kind of solution with a special laucher with a classloader that builds up correct classpath at runtime is a strategy that may resolve several project dependent classpath issues.

May be I'll try to extend the code of JUnitLoop for a kind of proof of conecpt of this idea.

[mirkoseifert]

I'd greatly approve steps into this direction as I agree that a special launcher (or JUnit test runner) will solve multiple problems. Let me know if things get concrete. I'm happy to entertain and discuss solution sketches.