You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/22 00:41:17 UTC
[jira] Moved: (SUREFIRE-261) Unable to generate the surefire report
if the project is not a java project, but tests are written in JAVA
[ http://jira.codehaus.org/browse/SUREFIRE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIREREP-28 to SUREFIRE-261:
---------------------------------------------------
Affects Version/s: (was: 2.0 Report Plugin)
Key: SUREFIRE-261 (was: MSUREFIREREP-28)
Project: Maven Surefire (was: Maven 2.x Surefire report Plugin)
> Unable to generate the surefire report if the project is not a java project, but tests are written in JAVA
> ----------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-261
> URL: http://jira.codehaus.org/browse/SUREFIRE-261
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Christophe DENEUX
> Attachments: MSUREFIREREP-28.patch
>
>
> I have a maven project with a POM packaging in which I run test with the maven-surefire-plugin. All works fine, but I am not able to generate the surefire report.
> After investigations in the source code of the maven-surefire-report-plugin, it seems to me that the implementation of the method SurefireReportMojo.canGenerateReport is not correct. The condition is too restrictive. It seems to me that the condition should be something like "Does a surefire execution report exist?".
--
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