Re: Possible surefire bug in -Dsurefire.failIfNoSpecifiedTests=false

I guess the reason is "intent", failIfNoTests=false if some module doesnt have any test but failIfNoSpecifiedTests=true if you asked to execute a test which was not foundbut agree surefire config is a bit complex upfront. Romain Manni-Bucau @rmannibucau | Blo

Re: Possible surefire bug in -Dsurefire.failIfNoSpecifiedTests=false

OK, looks like the problem is on our end, though the separation between -DfailIfNoTests and -DfailIfNoSpecifiedTests is strange and confusing. I don't see why both are needed. failIfNoTests seems to be a superset of failIfNoSpecifiedTests On Thu, Apr 7, 2022 at 11:33 AM Romain Manni-Bucau wrote:

Re: Possible surefire bug in -Dsurefire.failIfNoSpecifiedTests=false

It is there since v2.something IIRC, did you check with -X it was really set to false? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: Possible surefire bug in -Dsurefire.failIfNoSpecifiedTests=false

On Thu, Apr 7, 2022 at 11:16 AM Romain Manni-Bucau wrote: > > Hi Elliotte, > > Did you mean -DfailIfNoTests=false? the NoSpecified is for the case you > specify a test (-Dtest) IIRC. > No, the error message we see (and didn't see a couple of days ago) is: Failed to execute goal org.apache.maven.

Re: Possible surefire bug in -Dsurefire.failIfNoSpecifiedTests=false

Hi Elliotte, Did you mean -DfailIfNoTests=false? the NoSpecified is for the case you specify a test (-Dtest) IIRC. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Possible surefire bug in -Dsurefire.failIfNoSpecifiedTests=false

I'm still debugging our local project, but my team seems to be experiencing a problem where surefire fails projects without tests even though -Dsurefire.failIfNoSpecifiedTests=false is set. This happened suspiciously close in time to the recent 3.0.0-M6 release and our upgrade to the same. I'm by