Thank you for this very good hint! Indeed, at command line the test simply was skipped. When renaming it (so it ends on "*Test") the same problem occurs at CLI, too!
So it is definitively not a m2e problem! Thanks! :-) Markus -----Ursprüngliche Nachricht----- Von: m2e-users-boun...@eclipse.org [mailto:m2e-users-boun...@eclipse.org] Im Auftrag von Greg Thomas Gesendet: Dienstag, 24. Juli 2012 14:14 An: Maven Integration for Eclipse users mailing list Betreff: Re: [m2e-users] JUnit runs well using "Run As > Maven test" but fails at "Run As > JUnit test" On 24 July 2012 13:10, Markus Karg <k...@quipsy.de> wrote: > Well, "canBeEdited" is the Unit Test itself, so it cannot be the > source, as it runs well in mvn (and, BTW, it does nothing but simply > creating an instance of a class). By default, de.quipsy.entities.ProjectAPQPCompliance.canBeEdited is not a class that will automatically be run by Maven; http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html "By default, the Surefire Plugin will automatically include all test classes with the following wildcard patterns: ..." Are you sure that that class is actually being run when called via Maven? Greg _______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users _______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
