Thanks, this mechanism of toolchains seems useful, I was not aware of
it. In this particular scenario however, I would prefer to avoid having
to create a symlink manually if possible…
I think it is a fairly reasonable expectation that if a software
component is looking for a binary, it looks for i
Hi Elliotte,
Thanks! I have done so here, I hope I did not get too many things wrong:
https://issues.apache.org/jira/browse/MJAVADOC-646
Best,
Antonin
On 24/03/2020 20:31, Elliotte Rusty Harold wrote:
> I suggest filing an RFE in the Jira, and perhaps then sending a PR.
>
> I actually hit this
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
Both stack overflow answers are missing the solution I would choose:
toolchain[1]
This makes it possible to refer to a different JDKs compared to the runtime JDK
used by Maven.
However, having /usr/bin/javadoc doesn't follow the expected folder structure,
because toolchain will look for /bin/ja
