[
https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-24547:
------------------------------------
I would suggest that if you want different defaults when running itests, that the itests
root pom set that different default.
For example:
https://github.com/jbosstools/jbosstools-server/pull/516
Otherwise I don't see a way to have useUIThread = true AND false in the same parent
pom property.
Or, you could use the `mvn clean verify -P ITests` to enable the ITests profile in parent
pom which sets *useUIThread = false*, but that will also set the property false for unit
tests too.
It's probably best to set the values you want at the itests/pom.xml level, so you
override the default set for running unit tests.
Refactor ITests settings in parent pom
--------------------------------------
Key: JBIDE-24547
URL:
https://issues.jboss.org/browse/JBIDE-24547
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, integration-tests
Reporter: Pavol Srna
Assignee: Pavol Srna
Fix For: 4.5.0.AM1
It is desired that single 'mvn clean verify' command will run *unit tests* and
*integration tests* in a single run. Parent pom should hold all shared settings across
jbosstools repositories (e.g pluginCustomization, useUIThread etc ).
The problem is that unit tests require useUIThread=true, but integration tests the
opposite. We need to come with a solution where we share the settings in parent pom.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)