Please show support / vote for toolchain support in java action

Github Actions become very popular to build maven projects, but currently misses a convenience way to setup the java versions. There is currently on-going work to better support this: https://github.com/actions/setup-java/issues/276 it would be great if you could leave a comment (or even revie

Re: AbstractMethodError at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument

On Mon, Jul 11, 2022 at 10:42 AM Tamás Cservenák wrote: > > Howdy, > > seems m-site-p 3.11.0 introduced something that broke Maven2 (!!) jdepend > plugin (comes from parent). > > I could make it work like this > mvn clean package org.apache.maven.plugins:maven-site-plugin:3.10.0:site > -DskipTests

Re: MojoExecutionException and MojoFailureException

Here you go. https://issues.apache.org/jira/browse/MSHARED-1032 On Mon, 11 Jul 2022, 20:21 Benjamin Marwell, wrote: > > Please note there are more exceptions, e.g. in reporting. That's always > been a problem. Not sure, but I must have opened an issue for this > somewhere. > > Just for the s

Re: MojoExecutionException and MojoFailureException

Please note there are more exceptions, e.g. in reporting. That's always been a problem. Not sure, but I must have opened an issue for this somewhere. Just for the sake of completeness. On Mon, 11 Jul 2022, 14:12 Guillaume Nodet, wrote: > Yes, that's why I only kept a single exception in the ne

Re: AbstractMethodError at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument

Howdy, seems m-site-p 3.11.0 introduced something that broke Maven2 (!!) jdepend plugin (comes from parent). I could make it work like this mvn clean package org.apache.maven.plugins:maven-site-plugin:3.10.0:site -DskipTests (package was needed as then japicmp would fail) HTH T On Mon, Jul 11

Re: AbstractMethodError at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument

My Maven (3.6.3 + Java 11) also hit the same error from the command, but gave a better explanation: [INFO] Generating "JDepend" report --- jdepend-maven-plugin:2.0:generate-no-fork [WARNING] An issue has occurred with jdepend-maven-plugin:2.0:generate-no-fork report, skipping LinkageError Re

maven-war-plugin packagingExcludes not working

Dear all, I am trying to exclude the resources under ‘src/main/resource/db/*’ from being included in my war file any possible configuration of the ‘packagingExcludes ‘ config parameter seems to be ignored: My plugin-configuration as reported during the run with debug option is: [DEBUG] -

AbstractMethodError at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument

Hi All, I'm looking for help in how to remedy an AbstractMethodError at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument Running: git clone https://gitbox.apache.org/repos/asf/commons-dbcp.git cd commons-dbcp maven clean site -DskipTests Any thoughts? [INFO] Generatin

Re: MojoExecutionException and MojoFailureException

Yes, that's why I only kept a single exception in the new API. Le lun. 11 juil. 2022 à 13:59, Romain Manni-Bucau a écrit : > It got aligned AFAIK -> > > https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/MojoExecutor.java#L382 > > Romain Mann

Re: MojoExecutionException and MojoFailureException

It got aligned AFAIK -> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/MojoExecutor.java#L382 Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: MojoExecutionException and MojoFailureException

I might be wrong, but in case of "build FAILURE" only a short error is printed saying user should enable -X while with "BUILD ERROR" the exception is printed, maybe with a hint not to blame maven :-) Am 11.07.22 um 13:43 schrieb Romain Manni-Bucau: Hi, In all discussions about this topic it s

Re: MojoExecutionException and MojoFailureException

Hi, In all discussions about this topic it seems that this distinctions never had been useful so there seems to be an agreement to get a single exception "something went wrong in the mojo". Guess at the end being finer grain is not that useful for end user and makes writing mojo harder but I agree

Re: MojoExecutionException and MojoFailureException

Howdy, and along this line... BUILD FAILURE - uncompilable source, test failed, badly configured plugin, missing something from build, etc. all the issues that user CAN (and should) fix to have build pass, usually by editing sources, POM or settings. BUILD ERROR - disk full, no perm to write to d

Re: MojoExecutionException and MojoFailureException

Howdy, AFAIR one of the reasons for these two exceptions were to distinguish cases like: * expected exception during execution of Mojo: most typical, uncompilable source, or bad config/param, or something alike, condition the user CAN (and should) fix, usually by editing sources, POM or settings.