Now to find the smallest JRE to bundle and figure out if we need to produce 32 and also 64 bit versions of everything. When he do so, we take the supplied path and define a new custom environment variable to it. That is quite attractive, so I'm pretty convinced there are more pro's to bundling a JRE than drawbacks. Lately, we changed our Install4j installation mechanize in that we won't bundle an inner JRE anymore, but the customer has to supply a link to it. The bundled JRE is also one less thing for the bot servers as well. If there are complaints of the download being too large after we switch to mp3 then we should consider creating multiple build artifacts. So unless someone asks for minified DL size, let's stick to bundling a JRE. These days download size is less important, and if someone is going to DL 200MB, they can probably wait to DL another 30 or 50MB of JRE too. The macOS, Windows and Linux installers bundle a JRE in the. It looks like download size vs more control and simpler UX. Jalview is an application that uses a Java Runtime Environment (JRE) to run. I'm reading around to try and see what best practices are. The JRE that was mentioned I could not find anywhere, so I added a JRE simply to get things working. They have created lots of problems for our customers (and consequently for us) since JRE binaries only work for a certain range of. We have discontinued the official JREs bundles for Linux and Unix. Your instructions did not include where to get a JRE and I never opened install4j via GUI. It is still possible to create your own JRE bundles on Linux with Project->Create a JRE bundle and the bin/createbundle command line utility. #263, could you compare the size of the two different JRE options? If the one install4j has is smaller would you submit a PR against the assets repo to update the assets there. Reply to this email directly or view it on GitHub Unfortunately, it is not possible to change this behavior. Please reinstall or define EXE4JJAVAHOME to point to an installed JDK or JRE. That token I think we are inviting trouble by not using the system JRE when That is why java.exe will load DLL dependencies from the bin directory before looking in the system32 directory, The install4j launcher does not call java.exe, but starts the JVM via JNI so it's not the bin directory of the JRE but the directory of the launcher that is looked at first. The JVM found at java.exe path is damaged. Understand why their careful chosen JRE choice is not being respected. I see it inviting issues where users complain that theīundled JRE we force on them does not work on their system and they do not "Controlling" the JRE maybe has benefit, but practically I can't think ofĪnything specific. I guess it's probably worth asking if we should use system or bundled. So really the question is, if bundled, which bundle. I prefer bundledīecause that way we can control the users Java version." There is an option in install4j for using system/bundled. I see that change you made, and I do not like it. Maybe it has some extra required meta embedded, orĬould be in the long run. I'm failing to understand why the bundled Java should not work?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |