]
Alexey Kazakov commented on JBIDE-19081:
----------------------------------------
We don't plan to roll that out to all the projects. Because we know that some projects
will stick with the old pattern. JavaEE, JST and maybe others too. And yes we can create
individual tasks for components which could benefit form this change.
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