4 ms·
Maven is overly rigid. Years ago, i worked on a project where it made sense to have two integration test tasks - main tests and some special separate set of te
by twic 6y ago
Maven is overly rigid.
Years ago, i worked on a project where it made sense to have two integration test tasks - main tests and some special separate set of tests, i forget why. In Gradle, that's trivial. In Maven, it is impossible. You would have to write a new plugin which duplicates the existing integration test plugin to do it.
Maven runs the stages of the build in a fixed order, defined by the plugin code. If you have a reason to run two stages in a different order, bad luck, that can't be done.
There are tons of things like this.
- jdmichal 6y agoI'm pretty sure I've done this before... Maven is generally nothing more than some plugin executions with default configurations bound to specific phases. Both `surefire` and `failsafe` plugins allow you to configure the pattern of files executed (via `includes`). So you should be able to easily configure three executions, all with mutually-exclusive file patterns, one unit-test and two integration-tests. And you can choose whether or not to bind them to phases or run them manually.