I would go the other way round and remove the surefire plugin instead as
there are even more testing framework providers and not all can/want use
surefire.
So for me less is more and disabling it in case it is not wanted is
always a bit cumbersome. Then everyone can simply configure in their
parent pom whats wanted by default.
Am 05.09.25 um 07:56 schrieb Rüdiger:
Hiho!
I was wondering, what you all think about adding the failsafe plugin to the
super pom of maven 4. I often work with young teams, and it's difficult to
explain, why the surefire plugin works out of the box, but the failsafe plugin
does not... and of course, it's a nuisance to have to add it to every project.
Maybe unit tests used to be more important than integration tests in the past,
but my perception is that this is changing: ITs become more and more the
primary way of testing, while unit tests become more optional and focus on more
complex algorithms.
Kind regards
Rüdiger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
