How can make the Cargo Maven2/Maven3 plugin skip if tests are disabled?


At the moment even if I try to use all known flags to disable tests, the plugin still try to start only to report that test are skipped.

Taking too much time to build (just to start container) doesn't make it a major problem, but is definitely undesirable time overhead.

The real problem is that it makes it impossible to build software without special environment setup (for example, making sure port numbers required for container are not in use, pre-deployed external container, required values environment variables, etc.).

If container start fails (without any need to start it with disabled tests), such option to simply build software is not easily available anymore.

Container shouldn't be even started if tests are disabled.


S. Ali Tokmen


Alexey Pakseykin


Fix versions