Validating maven-surefire-plugin providers (dynamically loaded)

[cobratbq]

Is your feature request related to a problem? Please describe.
Currently, maven-surefire-plugin loads libraries at run-time based on which testing frameworks are in use in the codebase. These providers are not validated due to not being declared as dependency in the project configuration.

Describe the solution you'd like
Within reason, all loaded dependencies to be validated before use. Specifically for this issue:

Prematurely resolving and validating all surefire-providers, such that whatever maven-surefire-plugin decides to use is validated already. (The surefire-providers aggregator POM could be used. Version decided by taking version of maven-surefire-plugin that is used.)

Describe alternatives you've considered

• Skipping: that is the present solution. A warning is emitted to make the user aware.
• Scanning the local repository: although feasible, it means we can only validate after first use as these are resolved at run-time right before being executed.

Additional context
See code-base, specifically ArtifactResolver.java

NOTE: so far, I have not found a way to resolve the POM artifact as such and read the modules from it. It might require manually downloading the POM file and reading it with a lower-level maven API.

[slawekjaranowski]

We can check if dependency:go-offline works in this case ...

if yes we can see how dependency are resolved in dependency plugin.