[SUREFIRE-464] Default for failIfNoTests should be false

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.4, 2.4.1, 2.4.2
• Component/s: Maven Surefire Plugin
• Assignee: Unassigned
• Reporter: Dain Sundstrom
• Created: 01/Mar/08 14:00
• Updated: 20/Dec/19 11:39
• Resolved: 17/Mar/08 20:42

Description

In maven the surefire plugin executes by default when ever I build, and since the default for failIfNoTests is now true all of my modules must have at least one test or I must manually configure the plugin to not fail. This is a minor annoyance for single module builds but is a major pain when you have lots of modules. In my case it is extremely annoying since we have example modules we distribute that don't extend or parent pom (so users don't have to pull down our whole code base to get an example project).

This also means that the syntactic sugar "-Dtest=false" to turn off all testing no longer works.

At the end of the day, I don't understand why not having tests is a build failure and not just a warning.

Issue Links

• is duplicated by: SUREFIRE-778 failIfNoTests=false should not be required when using -Dtest=MyTestClass in multi-module reactor builds