<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Feb 26, 2025, at 3:59 PM, Alexey Semenyuk <asemenyuk@openjdk.org> wrote:</div><br class="Apple-interchange-newline"><div><div>On Tue, 25 Feb 2025 16:14:22 GMT, Alexey Semenyuk <asemenyuk@openjdk.org> wrote:<br><br><blockquote type="cite"><blockquote type="cite">- Fix the warning message about the custom installation directory location jpackage issues for DMG runtime packaging.<br> - Don't issue the warning when the `--install-dir` value equals the default installation directory location.<br> - Add relevant tests.<br></blockquote><br>Alexey Semenyuk has updated the pull request incrementally with one additional commit since the last revision:<br><br> Better warning wording<br></blockquote><br>Are there any strong objections against showing the warning only when `--install-dir` is set to the non-default value for DMG packaging?<br><br>-------------<br><br>PR Comment: https://git.openjdk.org/jdk/pull/23752#issuecomment-2686296919<br></div></div></blockquote></div><br><div>Thank you for helping me to understand the issue.</div><div><br></div><div>My opinion would still be that the warning should always be used since the parameter isn’t valid in this usage and not doing anything. If my understanding is in fact correct. Not a strong objection though.</div><div><br></div><div>After seeing this I was somewhat curious about the runtime packaging you mentioned.</div><div><br></div><div>The only reference I came across on some quick googling was here…</div><div><br></div><div><a href="https://www.herongyang.com/Java-Tools/jpackage-What-Is-It.html">https://www.herongyang.com/Java-Tools/jpackage-What-Is-It.html</a></div><div><br></div><div>I copied my current /Library/Java/JavaVirtualMachines/jdk-22.0.1.jdk to a rt directory and ran…</div><div><br></div><div>jpackage -n rt -t dmg --runtime-image rt</div><div><br></div><div>The resulting dmg had </div><div><br></div><div><div>ls /Volumes/rt/rt/Contents/Home</div><div>jdk-22.0.1.jdk</div></div><div><br></div><div>The actual runtime image is a couple directories deep. I tried removing my jdk22 and putting this into JavaVirtualMachines and it didn’t find it. </div><div><br></div><div><div>/usr/libexec/java_home</div><div>/Library/Java/JavaVirtualMachines/jdk-22.0.1.jdk/Contents/Home</div></div><div><br></div><div>Or </div><div><br></div><div><div>java -version</div><div>openjdk version "21.0.1" 2023-10-17</div><div>OpenJDK Runtime Environment (build 21.0.1+12-29)</div><div>OpenJDK 64-Bit Server VM (build 21.0.1+12-29, mixed mode, sharing)</div></div><div><br></div><div>Given the original dmg directory structure I tried…</div><div><br></div><div>jpackage -n rt -t dmg --runtime-image rt/jdk-22.0.1.jdk/Contents/Home</div><div><br></div><div>For some reason this dmg would’t open.</div><div><br></div><div>Is my usage incorrect or dmg not actually the type that should be used for this?</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>