[jira] Created: (SUREFIRE-505) Excludes Surefire reports for POM files with pom packaging

["Vincent Siveton (JIRA)" <ji...@codehaus.org>]

Excludes Surefire reports for POM files with pom packaging
----------------------------------------------------------

                 Key: SUREFIRE-505
                 URL: http://jira.codehaus.org/browse/SUREFIRE-505
             Project: Maven Surefire
          Issue Type: Improvement
          Components: report plugin
    Affects Versions: 2.4.3
            Reporter: Vincent Siveton


need to implement canGenerateReport()

-- 
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: (SUREFIRE-505) Excludes Surefire reports for POM files with pom packaging

["Andreas Sewe (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/SUREFIRE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206077#action_206077 ] 

Andreas Sewe commented on SUREFIRE-505:
---------------------------------------

I complained about this on the maven-users list (before I stumbled upon this ticket...): [http://www.mail-archive.com/users@maven.apache.org/msg105588.html]. 

But contrary to the ticket's title, I don't think that Maven plugins have be smart enough to detect the kind of
packaging used.

{quote}
In fact, the more I think about it, the more I come to the conclusion that making a plugin's behavior depend on the project's packaging is a bad idea; this would turn the project's packaging into a (non-obvious) flag. 

What would solve the problem nicely, though, is better communication between the maven-surefire-plugin and the maven-surefire-report-plugin: All that is required is for the former to generate its surefire-reports even if no unit tests were found. Then the maven-surefire-report-plugin could decide, based on the presence or absence of the surefire-reports whether to add its "Surefire Report" or not. (When the packaging is "pom" surefire:test is not bound to the lifecycle; no surefire-reports and thus no "Surefire Report" will be generated.)
{quote}

This would require some kind of coordinate effort by the {{maven-surefire-plugin}} and the {{maven-surefire-report-plugin}}, but would IMHO be the cleanest solution.

> Excludes Surefire reports for POM files with pom packaging
> ----------------------------------------------------------
>
>                 Key: SUREFIRE-505
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-505
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Report Plugin
>    Affects Versions: 2.4.3
>            Reporter: Vincent Siveton
>
> need to implement canGenerateReport()

-- 
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