Support Maven Site Plugin 3.12.0+

[l0s]

This breaks backward compatibility with maven-site-plugin:3.4.x and possibly other old versions as well. A revision bump is recommended.

This commit updates the Maven plugin-related dependencies and modifies any code affected by breaking changes. Note, some artifact versions were specified using a common property. However, it appears those artifacts no longer follow the same versioning scheme.

Closes #1037

[hcoles]

Thanks for the report and the fix.

4.0 of the maven site plugin looks to be a milestone rather than an official release. Given that this will break compatibility with earlier releases I'm relunctant to merge this until there is an official release of the 4.0 branch.

An alternative would be to pull the reporting plugin out of the main codebase and release it independently as a project under https://github.com/pitest.

[l0s]

@hcoles thanks for taking a look. However, I verified that the issue also occurs with version 3.12.0. I updated the example project to reflect that. I also verified that this PR works with 3.12.0.

Moving the reporting plugin out of the main codebase would also make sense. It would avoid the need to override version properties from the parent POM. If you would like me to go that route, let me know.

[hcoles]

@l0s Does everything work for projects using 4.0 if pitest depends 3.12.0? If so, that seems like the easiest route forward.

[l0s]

@hcoles I pushed a commit that downgrades the maven-reporting-* dependencies to 3.1.0 instead of the 4.0 milestone. Unfortunately, I had to keep the Surefire dependencies on the latest milestone. Without those, I was seeing numerous ClassNotFoundException instances when running the unit tests. Let me know what you think of this approach and if you'd like me to continue investigating the issue with the Surefire dependencies.

[hcoles]

Thanks @l0s, I'll get this merged in for the 1.9.0 release.

[l0s]

Thanks!