I suggest filing an RFE in the Jira, and perhaps then sending a PR. I actually hit this myself yesterday, and it would have been nice if the javadoc plugin had found th binary in /usr/bin.
In general I'm in favor of defense in depth for these sorts of things. Check as many places as we know about before failing. On Sun, Mar 22, 2020 at 7:05 PM Antonin Delpeuch (lists) <[email protected]> wrote: > > Hi, > > tldr: I am wondering if it would make sense for the Javadoc plugin to > look for the javadoc binary on the $PATH as well. > > Running the javadoc plugin on a Debian with OpenJDK 12 fails with the > error: "Unable to find javadoc command: The environment variable > JAVA_HOME is not correctly set." > > As far as I can tell there is no javadoc binary anywhere in the OpenJDK > 12 distribution packaged for Debian. But I do have a /usr/bin/javadoc. > > So if the javadoc plugin looked for a javadoc binary in the PATH, it > would work out of the box on Debian with that JDK. > > This seems to be an issue many people run into: > > https://stackoverflow.com/questions/13961615/unable-to-find-javadoc-command-maven > > https://stackoverflow.com/questions/49472783/maven-is-unable-to-find-javadoc-command > > Should I do a pull request to also look for the binary in the PATH? > > Best wishes, > > Antonin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
