[
https://issues.apache.org/jira/browse/SUREFIRE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875212#comment-17875212
]
Wojtek commented on SUREFIRE-1460:
----------------------------------
> Library plexus-archiver 1.0 is not threadsafe.
> See this link Parallel builds in Maven 3.
> We have to wait for plugin version 3.0.0.
[~tibordigana] is it about this plugin:
[https://mvnrepository.com/artifact/org.codehaus.plexus/plexus-archiver] ? It
seems that it's already on version 4.x. Would that mean it would be possible to
make `maven-surefire-report-plugin` parallel?
('m running James Mail Server and it has 270 modules and for each module there
is a warning about `maven-surefire-report-plugin` not being thread-safe :-) )
> 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
(v8.20.10#820010)
