> On Oct 28, 2017, at 2:03 PM, Michael Hall <mik3h...@gmail.com> wrote: > >> On Oct 28, 2017, at 1:59 PM, Alan Bateman <alan.bate...@oracle.com> wrote: >> >> On 28/10/2017 15:12, Michael Hall wrote: >>> I think I may of raised this as an issue sometime earlier. >>> >>> I filed a bug report through bug report.java >>> We will review your report and have assigned it an internal review ID : >>> 9051382 . >>> >>> But as I recall earlier it was indicated that this involved files owned by >>> Apple. >> I think so, meaning it's the macOS installation and updates that add the sym >> links to /usr/bin. I don't think it's something that we can help with here, >> or even in OpenJDK. Once you set your PATH to the installation directory >> then you should be able to use jlink. >> >> -Alan > > So this means that without setting PATH the java command line tools are not > available on OS X? Or just new ones? Is there potential conflict for existing > commands pointed to out of /usr/bin? Or will that be assumed to work > correctly as-is indefinitely?
Not that I can’t set PATH. That works for me. I am just wondering about other Mac users who start running into this. I guess if they don’t have the legacy commands around nothing will be there and they will have to discover setting PATH?
