You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2006/12/19 03:58:41 UTC
[jira] Closed: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=all ]
Kenney Westerhof closed MSUREFIRE-151.
--------------------------------------
Assignee: Kenney Westerhof
Resolution: Fixed
Fixed in revision 488511 - fallback to surefire's JUnit provider which has POJO support.
TODO: split off the pojo support from the junit provider.
> 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
> Assigned To: Kenney Westerhof
> 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