You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2020/05/24 10:01:46 UTC

Problem with site generation - maven-site-plugin

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
[INFO] preparing maven-plugin-plugin:report report requires
'process-classes' forked phase execution
[INFO]
[INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
mojo-parent >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
mojo-parent ---
[INFO]
[INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
mojo-parent <<<
[INFO] 'process-classes' forked phase execution for
maven-plugin-plugin:report report preparation done
[INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-changes-plugin:2.11
[INFO] 1 report configured for maven-changes-plugin:2.11: github-report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-checkstyle-plugin:2.16
[INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2.144 s
[INFO] Finished at: 2020-05-24T11:50:11+02:00
[INFO] Final Memory: 30M/128M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
project mojo-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
java.lang.NoSuchMethodError: 'java.lang.Object
org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
[ERROR] strategy =
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar


This can be reproduced with 3.0.5 up to 3.6.1.

Versions 3.6.2 and 3.6.3 are working fine.

This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
...in contradiction to the site[1] which says it is requirement 3.0..

Or has someone a different explanation for this?

Kind regards
Karl Heinz Marbaise


[1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
On Mon, May 25, 2020 at 2:49 AM Hervé BOUTEMY <he...@free.fr> 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 classorlds in this plugin
that might be conflicting with the one we pull in transitively. The
stack trace here smells like a dependency conflict to me.


-- 
Elliotte Rusty Harold
elharo@ibiblio.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Hervé BOUTEMY <he...@free.fr>.
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 dependencies on classloaders: really need the 
stacktrace, because I know that the way such low level reporting plugin 
classloading exceptions are reported are reported at the end against maven-
site-plugin by Maven core, even if it was the reporting plugin that reported 
an issue to the maven-site-plugin

Regards,

Hervé

Le dimanche 24 mai 2020, 14:02:54 CEST Elliotte Rusty Harold a écrit :
> 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
> 
> <el...@ibiblio.org> wrote:
> > 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/19be00a9bf2a410abb71324
> > 87dc24055060b2c70#diff-600376dffeb79835ede4a0b285078036
> > 
> > It's not immediately clear to me how the classpath for all this is
> > pulling in an earlier version of plexus-utils since maven-site-plugin
> > declares that dependency directly, but that's what seems to be
> > happening.
> > 
> > On Sun, May 24, 2020 at 6:02 AM Karl Heinz Marbaise <kh...@gmx.de> 
wrote:
> > > 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
> > > [INFO] preparing maven-plugin-plugin:report report requires
> > > 'process-classes' forked phase execution
> > > [INFO]
> > > [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
> > > mojo-parent >>>
> > > [INFO]
> > > [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
> > > mojo-parent ---
> > > [INFO]
> > > [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
> > > mojo-parent <<<
> > > [INFO] 'process-classes' forked phase execution for
> > > maven-plugin-plugin:report report preparation done
> > > [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> > > [INFO] configuring report plugin
> > > org.apache.maven.plugins:maven-changes-plugin:2.11
> > > [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> > > [INFO] configuring report plugin
> > > org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> > > [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> > > [INFO] configuring report plugin
> > > org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> > > [INFO]
> > > ------------------------------------------------------------------------
> > > [INFO] BUILD FAILURE
> > > [INFO]
> > > ------------------------------------------------------------------------
> > > [INFO] Total time: 2.144 s
> > > [INFO] Finished at: 2020-05-24T11:50:11+02:00
> > > [INFO] Final Memory: 30M/128M
> > > [INFO]
> > > ------------------------------------------------------------------------
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> > > project mojo-parent: Execution default-site of goal
> > > org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> > > incompatibility was encountered while executing
> > > org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
> > > java.lang.NoSuchMethodError: 'java.lang.Object
> > > org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> > > [ERROR] -----------------------------------------------------
> > > [ERROR] realm =   
> > > plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> > > [ERROR] strategy =
> > > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> > > [ERROR] urls[0] =
> > > file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-sit
> > > e-plugin/3.9.0/maven-site-plugin-3.9.0.jar
> > > 
> > > 
> > > This can be reproduced with 3.0.5 up to 3.6.1.
> > > 
> > > Versions 3.6.2 and 3.6.3 are working fine.
> > > 
> > > This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
> > > ...in contradiction to the site[1] which says it is requirement 3.0..
> > > 
> > > Or has someone a different explanation for this?
> > > 
> > > Kind regards
> > > Karl Heinz Marbaise
> > > 
> > > 
> > > [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > 
> > --
> > Elliotte Rusty Harold
> > elharo@ibiblio.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
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
<el...@ibiblio.org> wrote:
>
> 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 immediately clear to me how the classpath for all this is
> pulling in an earlier version of plexus-utils since maven-site-plugin
> declares that dependency directly, but that's what seems to be
> happening.
>
> On Sun, May 24, 2020 at 6:02 AM Karl Heinz Marbaise <kh...@gmx.de> wrote:
> >
> > 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
> > [INFO] preparing maven-plugin-plugin:report report requires
> > 'process-classes' forked phase execution
> > [INFO]
> > [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
> > mojo-parent >>>
> > [INFO]
> > [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
> > mojo-parent ---
> > [INFO]
> > [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
> > mojo-parent <<<
> > [INFO] 'process-classes' forked phase execution for
> > maven-plugin-plugin:report report preparation done
> > [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> > [INFO] configuring report plugin
> > org.apache.maven.plugins:maven-changes-plugin:2.11
> > [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> > [INFO] configuring report plugin
> > org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> > [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> > [INFO] configuring report plugin
> > org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 2.144 s
> > [INFO] Finished at: 2020-05-24T11:50:11+02:00
> > [INFO] Final Memory: 30M/128M
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> > project mojo-parent: Execution default-site of goal
> > org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> > incompatibility was encountered while executing
> > org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
> > java.lang.NoSuchMethodError: 'java.lang.Object
> > org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> > [ERROR] -----------------------------------------------------
> > [ERROR] realm =    plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> > [ERROR] strategy =
> > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> > [ERROR] urls[0] =
> > file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar
> >
> >
> > This can be reproduced with 3.0.5 up to 3.6.1.
> >
> > Versions 3.6.2 and 3.6.3 are working fine.
> >
> > This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
> > ...in contradiction to the site[1] which says it is requirement 3.0..
> >
> > Or has someone a different explanation for this?
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> >
> > [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org



-- 
Elliotte Rusty Harold
elharo@ibiblio.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
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 immediately clear to me how the classpath for all this is
pulling in an earlier version of plexus-utils since maven-site-plugin
declares that dependency directly, but that's what seems to be
happening.

On Sun, May 24, 2020 at 6:02 AM Karl Heinz Marbaise <kh...@gmx.de> wrote:
>
> 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
> [INFO] preparing maven-plugin-plugin:report report requires
> 'process-classes' forked phase execution
> [INFO]
> [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
> mojo-parent >>>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
> mojo-parent ---
> [INFO]
> [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
> mojo-parent <<<
> [INFO] 'process-classes' forked phase execution for
> maven-plugin-plugin:report report preparation done
> [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-changes-plugin:2.11
> [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2.144 s
> [INFO] Finished at: 2020-05-24T11:50:11+02:00
> [INFO] Final Memory: 30M/128M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> project mojo-parent: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
> java.lang.NoSuchMethodError: 'java.lang.Object
> org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> [ERROR] -----------------------------------------------------
> [ERROR] realm =    plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar
>
>
> This can be reproduced with 3.0.5 up to 3.6.1.
>
> Versions 3.6.2 and 3.6.3 are working fine.
>
> This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
> ...in contradiction to the site[1] which says it is requirement 3.0..
>
> Or has someone a different explanation for this?
>
> Kind regards
> Karl Heinz Marbaise
>
>
> [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>


-- 
Elliotte Rusty Harold
elharo@ibiblio.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Hervé BOUTEMY <he...@free.fr>.
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 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

I fixed the issue by shading and older Xpp3DomUtils class into maven-reporting-exec

I'll release Maven Reporting Exec 1.5 soon, then Maven Site Plugin 3.9.1

Regards,

Hervé

Le lundi 25 mai 2020, 09:21:40 CEST Karl Heinz Marbaise a écrit :
> 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:
> > 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-si
> > te-plugin/detail/master/94/pipeline> 
> > Le dimanche 24 mai 2020, 12:01:46 CEST Karl Heinz Marbaise a écrit :
> >> 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
> >> [INFO] preparing maven-plugin-plugin:report report requires
> >> 'process-classes' forked phase execution
> >> [INFO]
> >> [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
> >> mojo-parent >>>
> >> [INFO]
> >> [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
> >> mojo-parent ---
> >> [INFO]
> >> [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
> >> mojo-parent <<<
> >> [INFO] 'process-classes' forked phase execution for
> >> maven-plugin-plugin:report report preparation done
> >> [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> >> [INFO] configuring report plugin
> >> org.apache.maven.plugins:maven-changes-plugin:2.11
> >> [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> >> [INFO] configuring report plugin
> >> org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> >> [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> >> [INFO] configuring report plugin
> >> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] BUILD FAILURE
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 2.144 s
> >> [INFO] Finished at: 2020-05-24T11:50:11+02:00
> >> [INFO] Final Memory: 30M/128M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> >> project mojo-parent: Execution default-site of goal
> >> org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> >> incompatibility was encountered while executing
> >> org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
> >> java.lang.NoSuchMethodError: 'java.lang.Object
> >> org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> >> [ERROR] -----------------------------------------------------
> >> [ERROR] realm =   
> >> plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> >> [ERROR] strategy =
> >> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> >> [ERROR] urls[0] =
> >> file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site
> >> -pl ugin/3.9.0/maven-site-plugin-3.9.0.jar
> >> 
> >> 
> >> This can be reproduced with 3.0.5 up to 3.6.1.
> >> 
> >> Versions 3.6.2 and 3.6.3 are working fine.
> >> 
> >> This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
> >> ...in contradiction to the site[1] which says it is requirement 3.0..
> >> 
> >> Or has someone a different explanation for this?
> >> 
> >> Kind regards
> >> Karl Heinz Marbaise
> >> 
> >> 
> >> [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
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:
> 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 Marbaise a écrit :
>> 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
>> [INFO] preparing maven-plugin-plugin:report report requires
>> 'process-classes' forked phase execution
>> [INFO]
>> [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
>> mojo-parent >>>
>> [INFO]
>> [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
>> mojo-parent ---
>> [INFO]
>> [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
>> mojo-parent <<<
>> [INFO] 'process-classes' forked phase execution for
>> maven-plugin-plugin:report report preparation done
>> [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
>> [INFO] configuring report plugin
>> org.apache.maven.plugins:maven-changes-plugin:2.11
>> [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
>> [INFO] configuring report plugin
>> org.apache.maven.plugins:maven-checkstyle-plugin:2.16
>> [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
>> [INFO] configuring report plugin
>> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2.144 s
>> [INFO] Finished at: 2020-05-24T11:50:11+02:00
>> [INFO] Final Memory: 30M/128M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
>> project mojo-parent: Execution default-site of goal
>> org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
>> incompatibility was encountered while executing
>> org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
>> java.lang.NoSuchMethodError: 'java.lang.Object
>> org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
>> [ERROR] -----------------------------------------------------
>> [ERROR] realm =    plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
>> [ERROR] strategy =
>> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
>> [ERROR] urls[0] =
>> file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-pl
>> ugin/3.9.0/maven-site-plugin-3.9.0.jar
>>
>>
>> This can be reproduced with 3.0.5 up to 3.6.1.
>>
>> Versions 3.6.2 and 3.6.3 are working fine.
>>
>> This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
>> ...in contradiction to the site[1] which says it is requirement 3.0..
>>
>> Or has someone a different explanation for this?
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>>
>> [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Problem with site generation - maven-site-plugin

Posted by Hervé BOUTEMY <he...@free.fr>.
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 Marbaise a écrit :
> 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
> [INFO] preparing maven-plugin-plugin:report report requires
> 'process-classes' forked phase execution
> [INFO]
> [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
> mojo-parent >>>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
> mojo-parent ---
> [INFO]
> [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
> mojo-parent <<<
> [INFO] 'process-classes' forked phase execution for
> maven-plugin-plugin:report report preparation done
> [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-changes-plugin:2.11
> [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2.144 s
> [INFO] Finished at: 2020-05-24T11:50:11+02:00
> [INFO] Final Memory: 30M/128M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> project mojo-parent: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
> java.lang.NoSuchMethodError: 'java.lang.Object
> org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> [ERROR] -----------------------------------------------------
> [ERROR] realm =    plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-pl
> ugin/3.9.0/maven-site-plugin-3.9.0.jar
> 
> 
> This can be reproduced with 3.0.5 up to 3.6.1.
> 
> Versions 3.6.2 and 3.6.3 are working fine.
> 
> This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
> ...in contradiction to the site[1] which says it is requirement 3.0..
> 
> Or has someone a different explanation for this?
> 
> Kind regards
> Karl Heinz Marbaise
> 
> 
> [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org