You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/09/30 17:50:00 UTC
[jira] [Created] (CAMEL-17028) Make it easier to set a custom
maven-failsafe timeout value
Claus Ibsen created CAMEL-17028:
-----------------------------------
Summary: Make it easier to set a custom maven-failsafe timeout value
Key: CAMEL-17028
URL: https://issues.apache.org/jira/browse/CAMEL-17028
Project: Camel
Issue Type: Improvement
Components: build system
Reporter: Claus Ibsen
Fix For: 3.x
By default the 300 seconds can sometimes be too low a value.
For example some of the aws tests runs longer. For example 14 min took it once on my laptop.
In the component/pom.xml I have to do this
- <forkedProcessTimeoutInSeconds>300</forkedProcessTimeoutInSeconds>
+ <forkedProcessTimeoutInSeconds>900</forkedProcessTimeoutInSeconds>
Maybe that 300 can be some kind of property placeholder, which you can then specify as -D or some way when running mvn verify
--
This message was sent by Atlassian Jira
(v8.3.4#803005)