[
https://issues.jboss.org/browse/JBIDE-12422?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12422:
----------------------------------------
In tycho-surefire-plugin, the argument in configuration block is
forkedProcessTimeoutInSeconds, it's a maven parameter, set to property
${surefire.timeout}. Before, we directly configured this argument in pom.xml.
The patch suppresses direct configuration of this argument to rely on the surefire.timeout
property instead, which is used by maven to set a default value to the
forkedProcessTimeoutInSeconds argument when nothing is set. It does not add a new
property, it just rely on surefire.timeout.
So there is no new property, but now setting surefire.timeout via command-line works.
Rely on surefire.timeout property for test to allow better control
from CLI
---------------------------------------------------------------------------
Key: JBIDE-12422
URL:
https://issues.jboss.org/browse/JBIDE-12422
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Affects Versions: 3.3.1, 3.4.0.M1
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
The timeout property is hardcoded in parent and other poms inside the
tycho-surefire-plugin configuration block. It makes that passing the surefire.timeout
property from command-line is not efficient.
Instead, we should fully rely on this property to control timeout, so we'll provide
ability to override its value from command-line
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira