You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2018/01/11 22:42:00 UTC

[jira] [Assigned] (SUREFIRE-1460) Support @threadSafe in maven-surefire-report-plugin

     [ https://issues.apache.org/jira/browse/SUREFIRE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana reassigned SUREFIRE-1460:
--------------------------------------

    Assignee: Tibor Digana

> Support @threadSafe in maven-surefire-report-plugin
> ---------------------------------------------------
>
>                 Key: SUREFIRE-1460
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1460
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Report Plugin
>    Affects Versions: 2.20.1
>            Reporter: Jeffrey Bennett
>            Assignee: Tibor Digana
>            Priority: Minor
>
> It would be nice if the maven-surefire-report-plugin supported @ThreadSafe for the report-only goal.  While typical use of this plugin is within <reporting> (where I suspect threadsafety is of lesser concern), we happen to tie this plugin to the post-integration-test phase to insure that developers always have convenient index.html views of test results for how the build went.  Developers are reluctant to add 'site' target as it generates a lot of reports they don't need when doing frequent builds, thus, having report-only as part of the regular lifecycle made sense for us.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)