Hervé Boutemy opened MSHARED-921 and commented
see MSITE-863 for context
this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...):
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 codehaus-plexus/plexus-utils#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
Affects: maven-reporting-exec-1.4
Issue Links:
- MSHARED-923 upgrade maven-shade-plugin to 3.2.4 to get Reproducible Build
("causes")
- MSITE-863 NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running reports with Maven versions < 3.6.1
("is required by")
Hervé Boutemy opened MSHARED-921 and commented
see MSITE-863 for context
this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...):
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 codehaus-plexus/plexus-utils#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
Affects: maven-reporting-exec-1.4
Issue Links:
("causes")
("is required by")