TLDR; issue fixed :)
tracked in https://issues.apache.org/jira/browse/MSITE-863
fixed in maven-reporting-exec 1.5-SNAPSHOT
https://issues.apache.org/jira/browse/MSHARED-921
this is caused by Xpp3Dom class incompatibility with
Xpp3DomUtils.mergeXpp3Dom(...):
- Xpp3Dom version is taken from
On Mon, May 25, 2020 at 2:49 AM Hervé BOUTEMY wrote:
>
> removing Maven 2 code is a good simplification
> but FYI it won't remove dependency on plexus-classworld: it's the core of all
> plugins classloading mechanism to have independant plugins
>
Yes, but there's an explicit dependency on
Hi Hervé,
you can reproduce the issue on mojohaus parent repository
(github.com:mojohaus/mojo-parent.git) and using the branch "issue-105"
and just:
mvn site site:stage
Using Maven 3.5.2 fails with the described issue.
Kind regards
Karl Heinz Marbaise
On 25.05.20 08:41, Hervé BOUTEMY wrote:
removing Maven 2 code is a good simplification
but FYI it won't remove dependency on plexus-classworld: it's the core of all
plugins classloading mechanism to have independant plugins
didn't yet have time yet to dig, but perhaps the way maven-site-plugin invokes
reporting plugins causes some
uh, strange: maven-site-plugin ITs are ok with many Maven and JDK versions [1]
I'll need some time to investigate
Regards,
Hervé
[1]
https://builds.apache.org/blue/organizations/jenkins/maven-box%2Fmaven-site-plugin/detail/master/94/pipeline
Le dimanche 24 mai 2020, 12:01:46 CEST Karl Heinz
I still don't have full grasp of the cause, but I think we can remove
our dependency on plexus-classworlds completely by ripping out some
Maven 2 support. See
https://github.com/apache/maven-site-plugin/pull/24/f
On Sun, May 24, 2020 at 6:16 AM Elliotte Rusty Harold
wrote:
>
> getInputLocation
getInputLocation seems to have been added in plexus-utils 3.2.0.
The reproducible builds work for maven-site-plugin upgraded from
plexus 3.0.x to 3.3.0 in
https://github.com/apache/maven-site-plugin/commit/19be00a9bf2a410abb7132487dc24055060b2c70#diff-600376dffeb79835ede4a0b285078036
It's not
Hi to all,
I've stumbled upon the following problem during the site generation
mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:3.6.0
