It is there since v2.something IIRC, did you check with -X it was really set to false?
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 7 avr. 2022 à 13:28, Elliotte Rusty Harold <[email protected]> a écrit : > On Thu, Apr 7, 2022 at 11:16 AM Romain Manni-Bucau > <[email protected]> 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.plugins:maven-surefire-plugin:3.0.0-M6:test > (default-cli) on project protobuf-bom: No tests matching pattern > "**/*Test, !**/*IsValidUtf8Test, !**/*DecodeUtf8Test" were executed! > (Set -Dsurefire.failIfNoSpecifiedTests=false to ignore this error.) -> > [Help 1] > > However that is helpful. Now that I look, our command is setting > -DfailIfNoTests=false. It is not setting > -Dsurefire.failIfNoSpecifiedTests=false. I didn't initially catch the > difference because they were separated by many pages of log junk. is > failIfNoSpecifiedTests new in M6? Or is there some other reason this > might trigger now? > > > > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
