[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=comments#action_70859 ] Simon Kepp Nielsen commented on MSUREFIRE-151: ----------------------------------------------
No, I did not include any test frameworks on any classpath, as I do not have any test cases in my project (it only contains ressource files - no Java classes to test). The problem is, that the Surefire plugin is part of the default lifecycle for a project with JAR packaging, so it will be included automatically, even though i don't have any unit tests to run. In my case, this is not a major issue, as i can just add a test-dependency for JUnit or run maven with -Dmaven.test.skip=true. But if you are a newbie working on your first Maven "Hello World" project, you are likely to start with a very simple JAR project, with no test cases. In this case, you shouldn't have to do any work-arounds or complex configuration, in order to get your build running. > Surefire plugin fails if JUnit is not available > ----------------------------------------------- > > Key: MSUREFIRE-151 > URL: http://jira.codehaus.org/browse/MSUREFIRE-151 > Project: Maven 2.x Surefire Plugin > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Simon Kepp Nielsen > Priority: Critical > Attachments: error.txt > > > The Surefire Plugin fails with the following message, if JUnit is not > available on the test classpath: > [INFO] No Java test frameworks found > This means, that you have to include JUnit in the classpath, even for > projects that do not have any unit-tests (e.g. ressource projects or your > first Hello World project). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
