apache / apache/maven-surefire
[SUREFIRE-1460] Support @threadSafe in maven-surefire-report-plugin
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Jeffrey Bennett](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbennett2091)** opened **[SUREFIRE-1460](https://issues.apache.org/jira/browse/SUREFIRE-1460?redirect=false)** and commented
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 \ (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.
---
**Affects:** 2.20.1
1 votes, 3 watchers
Contributor guide
Research direction
Locate the maven-surefire-report-plugin implementation of the report-only goal and inspect how thread safety is declared for comparable Maven goals. Verify that report-only can support @ThreadSafe when used in the post-integration-test phase, while preserving its existing report generation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100