[
https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-22739:
----------------------------------------
This question is for all component leads. I can say what projects will NOT benefit from
that change for sure: javaee and jst. But it's up to component leads to decide if
their component would benefit. [~xcoulon], [~ibuziuk], [~gastaldi], [~koen.aers],
[~jeffmaury], [~adietish], [~rob.stryker], [~snjeza], [~gercan]
Use simpler Surefire include/exclude pattern in root poms
---------------------------------------------------------
Key: JBIDE-22739
URL:
https://issues.jboss.org/browse/JBIDE-22739
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Nick Boldt
Assignee: Alexey Kazakov
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)