[ 
https://issues.apache.org/jira/browse/SUREFIRE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750523#comment-16750523
 ] 

Tibor Digana commented on SUREFIRE-1626:
----------------------------------------

You can fix it in {{org.apache.maven.surefire.util.internal.ObjectUtils}}.
Feel free to open pull request on GitHub and provide a fix.

> Configuration possibility to disable the properties 
> "surefire.test.class.path" and "java.library.path"
> ------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1626
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1626
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.20, 2.21.0
>            Reporter: Pierre Labuhn
>            Priority: Minor
>
> The properties "{color:#444444}surefire.test.class.path{color}" andĀ  
> "{color:#444444}java.class.path{color}" 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({color:#444444}surefire.test.class.path{color}) and 
> SUREFIRE-1262 ({color:#444444}java.class.path{color}). {color:#333333}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.{color}
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to