Open Bukama opened 4 weeks ago
To be honest I'm not sure if this is a general Doxia/Site plugin issue, but after removing the JDepend Report-Dependency everything worked fine and we don't have any issues in all our other projects (which uses 4.0.0-Mx for a longer time but no JDepend. As the Mojo that throws the error is an JDepend Mojo according to message/stacktrace I decided to post it here (and after a quick question in Maven Slack)
I ran into a similar problem within apache-tentacles as well after I updated to maven-site-plugin 3.12.1 to 3.20.0:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project apache-tentacles: Failed to render site: Error generating jdepend-maven-plugin:2.0:generate-no-fork report: UndeclaredThrowableException: InvocationTargetException: Method org/codehaus/mojo/jdepend/JDependNoForkMojo.generate(Lorg/apache/maven/doxia/sink/Sink;Ljava/util/Locale;)V is abstract -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project apache-tentacles: Failed to render site
.....
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error generating jdepend-maven-plugin:2.0:generate-no-fork report
.....
Caused by: java.lang.AbstractMethodError: Method org/codehaus/mojo/jdepend/JDependNoForkMojo.generate(Lorg/apache/maven/doxia/sink/Sink;Ljava/util/Locale;)V is abstract
at org.codehaus.mojo.jdepend.JDependNoForkMojo.generate (JDependNoForkMojo.java)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at com.gradle.maven.cache.extension.h.b.lambda$createProxy$0 (SourceFile:82)
@slachiewicz Is the problem related to jdepend or a configuration issue? Thanks
@Bukama is the problem fixed with the current 2.1-SNAPSHOT? If so maybe a release can be done as the current situation (with v2.0) yields an empty report or a broken build. Thanks.
@Bukama is the problem fixed with the current 2.1-SNAPSHOT? If so maybe a release can be done as the current situation (with v2.0) yields an empty report or a broken build. Thanks.
Hey, sadly I can't check as the SNAPSHOT is not available via Maven Central and cloning Github project is blocked by our security here :/ . As only dependencies from Maven Central and verified by our comapnies Nexus IQ servers can be used - is it possible to release a beta/RC or so? I have seen there are tags for beta versions of former versions.
We updated the Maven-plugins (compile, jar, site, etc.) of one of our projects. This project is the only one that also uses the jdepend-maven-plugin (can't tell you why). The build then threw a warning and could not generate a proper JDepend report.
The project had the following dependency in the report section
The warning is related to DOXIA so maybe to the site-plugin which is used in version
4.0.0-M14
(in which Doxia is updated for Maven 4 etc). Issues doesn't seem to pop with site-plugin3.12.1
Not very surprising that the JDEpend-Report is not generated correctly with that warning