[
https://issues.apache.org/jira/browse/MNG-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6968.
-------------------------------
Fix Version/s: 3.7.0
Resolution: Fixed
Resolved by MNG-6548.
> Maven depends on ancient maven-site-plugin - upgrade dependency
> ---------------------------------------------------------------
>
> Key: MNG-6968
> URL: https://issues.apache.org/jira/browse/MNG-6968
> Project: Maven
> Issue Type: Bug
> Reporter: Graham Leggett
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.7.0
>
>
> 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:
> https://github.com/apache/maven/commit/4ec06bf67cc6bdffa026f46c5836e3bc895865ed
> Looks like until maven is fixed to respect the POM, we need to upgrade the
> hard coded dependencies to be something not ancient.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
