jnlp apply to HKMU (switches between hklm and hkcu depending on machine or user installation)Īdding/splitting the installer features in two groups will break actual feature level compatibility. To write "Oracle Java Key" you must write toīut a key must not be overridden with an older key ( always pointed to the latest/newest Java )Īs it depends of the version intended to be installed and already installed, just write reg key without the binary is useless and or/copy/paste reg key from one host to another is a bad idea. Seems really challenging to find "the right" solution! currently the installer executes logic to manipulate registry values directly, right? (via wix-tooling?)Ĭould the installer maybe also create windows cmd / batch files that make it possible to re-execute that same registry-setting commands for the specific version? (although I just peeked into c79c7e8 and that seems rather complicated :) ) Thank you for putting your time into this solution there, btw. i read your very informative comments (for example: #64 (comment)). Hi the supplied info in the deep link is probably just the tip of the iceberg, i suppose? would i not also need some kind of reg entry for the directory that this keys point to? orcl url sadly does not mention anything like that thereĭear please excuse my "pulling you in" by mentioning. See for the entries common Java software expects. The registry entries can be created manually using regedit. Enter "environment variable" into the search field of Windows and the right option should pop up. JAVA_HOME is an environment variable an can be set using the GUI. could the functionality be transformed to a utility that could be distributed inside the zipped distribution? is there a way to reproduce the things the installer does concerning creation of the the required registry entries? scoop does not use the msi installer but extracts the zipped distribution. which is great! only i do not use the manual installer but use scoop to install java. With issue #64 you created a way to use the installer to handle the registry magic. but as i found the personally most fitting issue in this repo that is handling technicalities concerning the openjdk windows registry stuff i thought i post this issue here. i am open to recreating this issue somewhere else seen better fitting. I do not know where to address my question (am aware this repo is for the installer), please be kind if you think this is the wrong place. TL DR: How to handle registry magic when using zip distribution? (for example after installing via scoop installer)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |