Hi Tibor, I assume that what you said in your previous messages is correct and I simply do not understand it. E.g., I think I did not ask for Surefire to be executed in a later phase. That even feels wrong to me. My requirement is about whether failing tests make the build abort immediately or fail at the end in order to ensure that all tests in modules which compile successfully are executed.
So, lacking basic understtanding of what you described, I also do not feel comfortable simply quoting you and asking on another mailing list, because I do not intend to develop a Surefire or general Maven extension. I can only reiterate that I can describe **what** I want the build to do, not **how** it should be done. I think I described that in enough detail already. The "how" is up to you or whoever extends Surefire. That would be you or one of the other experienced committers or contributors. -- Alexander Kriegisch https://scrum-master.de Tibor Digana schrieb am 15.02.2022 17:08 (GMT +07:00): > I have realized that we can move straight ahead with the following. > Basically your expectations are to shift the concrete phase execution of > the build lifecycle to the end of the build. > > I can imagine a "generic" Extension and you would configure the Extension > so that the "test" phase or the "verify" phase to the end of the build. > > If you rephrase the question of this email and send it to the > d...@maven.apache.org, you > may receive an answer with an existing solution. > > I guess you are not the first person who has this requirement. > > >> On Tue, Feb 15, 2022 at 5:12 AM Alexander Kriegisch >> <alexan...@kriegisch.name >> <mailto:alexan...@kriegisch.name> > wrote: >> >>> I waited for a week in order to see other developers want to contribute >>> to the general discussion you asked to have before making any design >>> decisions the Surefire team might regret later. Did you get the input >>> your were looking for from somewhere off-list, or have you had enough >>> time to decide how you want to handle this? I am not sure I can >>> contribute more than I already have by explaining the potential >>> user/business value in other parts of this thread. >>> >>> >>> Tibor Digana schrieb am 07.02.2022 23:16 (GMT +07:00): >>> >>> > I can imaging to utilize afterSessionEnd() >>> > >>> https://maven.apache.org/ref/3.8.4/maven-core/apidocs/index.html?org/apache/maven/AbstractMavenLifecycleParticipant.html >>> > Maybe this is the way to do it in a clear way via Maven Extensions, >>> see >>> > >>> https://maven.apache.org/ref/3.8.4/maven-core/apidocs/index.html?org/apache/maven/eventspy/AbstractEventSpy.html >>> > https://maven.apache.org/studies/extension-demo/ >>> > >>> > and execute the Project's Mojo as if the Mojo was executed in a >>> traditional >>> > way. >>> > >>> > On Sat, Feb 5, 2022 at 5:27 AM Alexander Kriegisch >>> <alexan...@kriegisch.name >>> <mailto:alexan...@kriegisch.name> > >>> > wrote: >>> > >>> >> I know that this probably is a classic question, because there >>> suggested >>> >> answers on Stack Overflow (and maybe also somewhere here in this >>> mailing >>> >> list), but I did not found anything satisfying the following >>> criteria: >>> >> >>> >> 1. Run all Surefire tests, if compilation succeeds, also those of >>> >> dependent modules, even if there are tests with failurer or errors. >>> >> (We leave Failsafe out of the picture for now for simplicity's >>> >> sake, but basically the same would apply to Failsafe tests for >>> >> modules which can be compiled and packaged, despite failing >>> >> Surefire tests.) >>> >> >>> >> 2. Fail the multi-module build in the end for all modules with >>> failing >>> >> tests. >>> >> >>> >> I know there is '-fae', but it skips modules depending on ones with >>> test >>> >> failures. >>> >> >>> >> I know there is '-fn', but it falsely makes the whole build pass. >>> >> >>> >> I know that the Maven build lifecycle is based on module dependencies >>> >> and that dependent modules usually should not be built, if a >>> dependency >>> >> fails to build. But OTOH, the same build would pass with >>> '-DskipTests', >>> >> and the requirement that artifacts be compiled and packaged and >>> >> dependent modules built, because those artifacts can in fact be >>> compiled >>> >> and packaged, makes practical sense. Basically, the user wants test >>> >> failures reported correctly, but still make sure that as many tests >>> as >>> >> possible are being run. >>> >> >>> >> Is there any way to achieve that? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
