You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Simon Kepp Nielsen (JIRA)" <ji...@codehaus.org> on 2006/07/26 17:31:32 UTC
[jira] Created: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
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
[jira] Commented: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
Posted by "Jon SlinnHawkins (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
Posted by "David J. M. Karlsen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=comments#action_70810 ]
David J. M. Karlsen commented on MSUREFIRE-151:
-----------------------------------------------
Did you provide another supported test-framework like testNG on [at lease] the test scope?
AFAIK it's not possible to utilize surefire without one of these frameworks and something to actually test (e.g. resources would have to be tested through use of one of these)
> 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
[jira] Updated: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
Posted by "Mark Holster (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=all ]
Mark Holster updated MSUREFIRE-151:
-----------------------------------
Attachment: no-test-framework-patch.txt
The attached patch logs a warning if no test framework could be found and stops executing surefire.
> 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
[jira] Commented: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
Posted by "Simon Kepp Nielsen (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=all ]
Brett Porter updated MSUREFIRE-151:
-----------------------------------
Fix Version/s: 2.3
> 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
>
>
> 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
[jira] Moved: (SUREFIRE-99) Surefire plugin fails if JUnit is not
available
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-151 to SUREFIRE-99:
------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-99 (was: MSUREFIRE-151)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Surefire plugin fails if JUnit is not available
> -----------------------------------------------
>
> Key: SUREFIRE-99
> URL: http://jira.codehaus.org/browse/SUREFIRE-99
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> 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
[jira] Closed: (MSUREFIRE-151) Surefire plugin fails if JUnit is
not available
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ 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