[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=comments#action_72787 ] Jon SlinnHawkins commented on MSUREFIRE-151: --------------------------------------------
I am also having this problem. However it manifests itself slightly differently. I have a set of approved libraries for use across all of our development projects. one being junit. to ease the management of approved libs, we have created an inhouse groupid for them, but still using the original artifactId and version. if i include the inhouse junit jar i get the error described above. The only way i can get surefire to run is to use the junit/junit (groupId/artifactId). Surely having the junit jar on the classpath should suffice no matter what it's groupId is. Does the Surefire plugin reference the groupId/artifactId explicitly > 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 > Fix For: 2.3 > > Attachments: error.txt, no-test-framework-patch.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
