Maven 2.0.6 is out and it seems it fixes some problems. One really annoying issue with at least the last release 2.0.5 was, that maven tends to ignore some test in projects which subprojects contains both JUnit and TestNG test. I wrote about that problem and a solution if you are in the affected project, but the problem re-appears if you are building not from within the same directory level, e.g. one level up in the parent project. This seems to be fixed now...
No, it isn't. Does anybody know how to get all test run in a mixed unit test framework project?
Trackback URL for this post:
http://lepetitfou.dyndns.org/home/trackback/26
Can anybody tell me, why Maven behaves different on the same project structure but on different computers (both running Gentoo Linux)? Same maven version, same pom.xml's, same local settings.xml. The only difference is, that one ~/.m2/reporsitory contains "more history" then the other. This computer with more packages in the maven repository skips the above mentioned TestNG tests, the other runs them as awaited. How can one depend on a build system which is not predictable?
There are two posibilities: Someone point me to a better buildsystem for Java or I will try to develop one which is more like portage.
Post new comment