[MNG-6968] Maven depends on ancient maven-site-plugin - upgrade dependency

[jira-importer]

Graham Leggett opened MNG-6968 and commented

The maven release plugin (MRELEASE-1052) currently ignores versions of plugins specified in the POM, and in a pattern as yet not clearly explained chooses maven plugins hardcoded into maven itself.

One such plugin is the maven-site-plugin, which is the POM specified version in a normal build, but hard coded to the ancient v3.3 plugin when triggered from the maven-release-plugin.

Chaos ensues:

https://mkyong.com/maven/mvn-site-java-lang-classnotfoundexception-org-apache-maven-doxia-siterenderer-documentcontent/
https://stackoverflow.com/questions/51091539/maven-site-plugins-3-3-java-lang-classnotfoundexception-org-apache-maven-doxia
https://issues.apache.org/jira/browse/CRUNCH-671
https://stackoverflow.com/questions/51103120/why-does-maven-site-plugin-always-use-version-3-3

Digging leads us to this commit:

4ec06bf

Looks like until maven is fixed to respect the POM, we need to upgrade the hard coded dependencies to be something not ancient.

---

Issue Links:

• MNG-6548 Lifecycle plugin version upgrades
  ("depends upon")

Remote Links:

• GitHub Pull Request #382
  

Backported to: 4.0.0-alpha-2

[jira-importer]

Piotr Zygielo commented

I think it is related to MNG-6548.

[jira-importer]

Michael Osipov commented

Resolved by MNG-6548.