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

Posted to issues@camel.apache.org by "Freeman Yue Fang (Jira)" <ji...@apache.org> on 2022/01/24 21:48:00 UTC

[jira] [Resolved] (CAMEL-17546) Introduce camel.failsafe.forkTimeout property for maven-failsafe-plugin

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

Freeman Yue Fang resolved CAMEL-17546.
--------------------------------------
    Resolution: Fixed

> Introduce camel.failsafe.forkTimeout property for maven-failsafe-plugin
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-17546
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17546
>             Project: Camel
>          Issue Type: Wish
>          Components: build system
>            Reporter: Freeman Yue Fang
>            Assignee: Freeman Yue Fang
>            Priority: Minor
>             Fix For: 3.15.0
>
>
> currently the forkedProcessTimeoutInSeconds is hardcoded as 300 secs for maven-failsafe-plugin, it's not sufficient for some tests that need more time to finish.
> We'd better introduce a camel.failsafe.forkTimeout(the counterpart of existing camel.surefire.forkTimeout) and set it default value as 600 secs.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)