Ah, yes, we do have some needed duplication, I never use the stock release plugin. We have two custom plugins that are handy for releasing.
Gary On Wed, Jan 6, 2021, 07:14 Henri Biestro <hen...@apache.org> wrote: > > Found the culprit; it seems 'site' plugin uses the report section to > generate the javadoc whilst 'release' plugin uses the build section to do > the same. Fixed the issue by adding the same javadoc plugin configuration > in build section of the pom.xml. > > On 2021/01/05 17:05:32, Henri Biestro <hen...@apache.org> wrote: > > Hello Team; Happy new year! > > > > I'm trying (again) to release JEXL 3.2 and I'm stuck at the 'Maven > release plugin' step in https://commons.apache.org/releases/prepare.html. > > > > Despite the fact a 'maven site' from IntelliJ does succeed, a 'mv > release:prepare -DtryRun' fails generating the Javadoc with a: > > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-javadoc-plugin:3.2.0:jar (attach-javadocs) > on project commons-jexl3: MavenReportException: Error while generating > Javadoc: > > [INFO] [ERROR] Exit code: 1 - > /Users/henri.biestro/Java/Jexl/git/commons-jexl/src/main/java/org/apache/commons/jexl3/parser/SimpleNode.java:128: > warning: no description for @param > > > > The package is excluded in the configuration so I must be missing an > obvious step somewhere else to let maven do its magic properly. > > Any help appreciated :-) > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >