I would be more explicit to understand if the exception was with more context ... I think instead of just displaying that no test framework was found the plugin should tell that it did not found either junit:junit or testng:testng ... in the list of reactors or what ever. that way we would now better what's going on, and should someone use a different/corporate test framework maybe let the opportunity to set it up from configuration ... -- View this message in context: http://www.nabble.com/-m2-+No+Java+test+frameworks+found--t1682690.html#a4606866 Sent from the Maven - Users forum at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
