[
https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19081:
------------------------------------
With this successfully applied in Base, but nowhere else...
is the plan to roll that out to all the projects? Maybe we want to split the jira into 15
child tasks, one per project?
then when everyone has reviewed if they're better/worse after the change, and everyone
has done it, we can move the change into parent pom instead of being controlled at the
per-project level
[~fbricon] [~akazakov] wdyt?
Use simpler Surefire include/exclude pattern in parent pom
----------------------------------------------------------
Key: JBIDE-19081
URL:
https://issues.jboss.org/browse/JBIDE-19081
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
Fix For: 4.4.x
1. In JBDS9, use these new default patterns for Surefire to define which test classes to
run/exclude:
{code}
include = *Test*, *Test, *TestCase
exclude = *Abstract*
{code}
2. If that causes test failures because running incorrectly named
abstract stuff, they can refactor, add their own root pom overrides, use
a TestSuite, or use @Ignore in test classes.
3. If the count of tests run suddenly DROPS because the pattern isn't
running the correct # of tests, they can add their own root pom
overrides, or use a TestSuite.
Ref:
http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)