You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/07/20 09:50:01 UTC

[jira] [Resolved] (OAK-9501) Don't trim stack traces during unit tests and ITs

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

Konrad Windszus resolved OAK-9501.
----------------------------------
    Fix Version/s: 1.42.0
       Resolution: Fixed

Fixed in https://github.com/apache/jackrabbit-oak/commit/023f63235d0f0ea1076f31573e3114436e298465.

> Don't trim stack traces during unit tests and ITs
> -------------------------------------------------
>
>                 Key: OAK-9501
>                 URL: https://issues.apache.org/jira/browse/OAK-9501
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: parent
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 1.42.0
>
>
> By default m-surefire-p and m-failsafe-p trim stack traces which makes it hard to debug issues in tests. This often removes crucial information (compare with https://issues.apache.org/jira/browse/SUREFIRE-1798), therefore we should disable trimming.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)