apache / apache/maven-surefire
[SUREFIRE-1626] Configuration possibility to disable the properties "surefire.test.class.path" and "java.library.path"
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Pierre Labuhn](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pierre_labuhn)** opened **[SUREFIRE-1626](https://issues.apache.org/jira/browse/SUREFIRE-1626?redirect=false)** and commented
The properties "surefire.test.class.path" and "java.class.path" which are written into surefire reports can become quite large in bigger projects since the version 2.21.0.
The changes responsible for that are SUREFIRE-1254(surefire.test.class.path) and SUREFIRE-1262 (java.class.path). Since then the size of these two properties are considerably greater than before. As far as I could analyse the code, there is no configuration possibility to remove both of these properties in the surefire report files.
Therefore it a configuration possibility should be built in to disable the properties in case they are not needed.
This improvement is created because in our project we have the issue, that our CI environment is having issues while creating the surefire reports because of the file size.
The current Workaround is to truncate both of these properties to minimize the file size of each report.
---
**Affects:** 2.20, 2.21.0
Contributor guide
Research direction
The issue names no source files, tests, or entry points. Start by tracing where Surefire report properties are generated, focusing on the surefire.test.class.path and java.class.path properties. Done means a configuration option can disable both properties and the resulting reports avoid the oversized values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100