I'm working from the command line following the steps outlined in the doc.
I can not fix the Javadoc because these classes are generated by javacc, the
whole package is intended to be ignored (excluded) and docLint is already off.
'mvn site' succeeds, 'mvn release:prepare -DtryRun' fails; it
I you are working toward a release, I recommend working with Maven on the
command line. You'll want to know exactly what is going on.
Gary
On Tue, Jan 5, 2021, 17:31 John Patrick wrote:
> What version of java is the command line maven using and what is
> intellij using for;
> 1. Settings ->
What version of java is the command line maven using and what is
intellij using for;
1. Settings -> "Build, Execution, Deployment" -> "Build Tools" ->
Maven -> Importing -> "JDK for importer"
2. Settings -> "Build, Execution, Deployment" -> "Build Tools" ->
Maven -> Runner -> "JDK for importer"
3.
You "should" fix the Javadoc warnings; -) or disable doclint.
Gary
On Tue, Jan 5, 2021, 12:06 Henri Biestro 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.
>
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
Hi,
this looks like a bug, since "e hene" in Albanian means Monday. [0]
Please file an issue, and let us know what the incident id is.
cheers,
dalibor topic
[0] https://en.wiktionary.org/wiki/e_h%C3%ABn%C3%AB
On 29.12.2020 19:27, Gary Gregory wrote:
Hi Rory and all,
Before I go through
