[ https://issues.apache.org/jira/browse/MSHARED-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408437#comment-17408437 ]
Hudson commented on MSHARED-921: -------------------------------- Build succeeded in Jenkins: Maven » Maven TLP » maven-site-plugin » MSITE-829 #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/MSITE-829/31/ > NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 > --------------------------------------------------------------------------- > > Key: MSHARED-921 > URL: https://issues.apache.org/jira/browse/MSHARED-921 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-exec > Affects Versions: maven-reporting-exec-1.4 > Reporter: Herve Boutemy > Assignee: Herve Boutemy > Priority: Major > Fix For: maven-reporting-exec-1.5 > > > see MSITE-863 for context > this is caused by Xpp3Dom class incompatibility with > Xpp3DomUtils.mergeXpp3Dom(...): > - Xpp3Dom version is taken from Maven core classloader as exported: see > [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] > - Xpp3DomUtils is taken from current plugin classloader > with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils > is a recent version (plexus-utils >= 3.2.0) that expects to merge the input > location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] > but older Maven core versions don't have this input location field in > Xpp3Dom, since they provide older plexus-utils that was upgraded to add > location tracking in MNG-6597 for Maven 3.6.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)