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 <nhoj.patr...@gmail.com> wrote: > 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. "Project Structure" -> Project -> "Project SDK" > > As when running maven tasks within IntelliJ, I can never remember > which of 1, 2 or 3 is used. > > 1 is used when importing and refreshing maven projects, so if you have > conditional profiles with activation based upon jvm, changing this > might be needed. > 2 i think is used when running tasks > 3 is used when writing code, validating code and also compiling code. > 3 i think is also used when running unit tests > > Not sure if that will show other issues of fix this issue, hopefully > it maybe highlight if different jvm's are being used when comparing > inside and outside intellij. > > John > > > On Tue, 5 Jan 2021 at 17:06, 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 > >
