[MacPorts] #67935: openjdk11-graalvm, openjdk17-graalvm, openjdk19-graalvm: buildbot activation fails: file LICENSE_NATIVEIMAGE.txt already exists and does not belong to a registered port

[MacPorts]

#67935: openjdk11-graalvm, openjdk17-graalvm, openjdk19-graalvm: buildbot
activation fails: file LICENSE_NATIVEIMAGE.txt already exists and does not
belong to a registered port
-------------------------------------------------+-------------------------
  Reporter:  mascguy                             |      Owner:  breun
      Type:  defect                              |     Status:  assigned
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.8.1
Resolution:                                      |   Keywords:
      Port:  openjdk11-graalvm,                  |
  openjdk17-graalvm, openjdk19-graalvm           |
-------------------------------------------------+-------------------------

Comment (by mascguy):

 Replying to [comment:3 ryandesign]:
 > My understanding was that Java on macOS must be installed (or symlinked)
 into /Library/Java/JavaVirtualMachines in order to work.

 Well, it's certainly beneficial to add symlinks there, since that's the
 standard macOS install location. (Which you folks already know, but just
 mentioning it for others who may be less familiar with all of these
 details.) And tools like `/usr/libexec/java_home` look there, when
 searching for installed JDKs. Ditto for Java-based apps and tools, if
 they're macOS-aware.

 So to provide the best experience to our users - and minimize the chance
 of issues - it makes sense to create a symlink in that location.

 > Installing in the MacPorts prefix and symlinking into the required
 system location in /Library is also the approach MacPorts base uses for
 launchd plists.

 Yep, exactly, which is why I'm advocating for installing in the MacPorts
 tree.

 Pondering this a bit more, it might be good to install JDKs under
 `${prefix}/Library/Java/JavaVirtualMachines/openjdkXXXX`, similar to how
 we handle Python and other components. But whichever area we choose, it
 would be preferable to installing directly to
 `/Library/Java/JavaVirtualMachines`.

 Thoughts all?

-- 
Ticket URL: <https://trac.macports.org/ticket/67935#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS