The content of the start.bat script (JREPATH is correctly set): start "" /b %JREPATH%\bin\javaw.exe -Xmx2g -jar WorkSheet.jarīut the start.bat works correctly when I start it manually! There is enough memory. When the InstallBuilder installer tries to execute the Java program from a start.bat script by the end of the installation, it fails with this error log: With Windows no problem the latest version installed is used. If during installation, the computer does not contain a java I install the embed version, but if I subsequently install a version on the system, the binaries generated by install builder does not use this version Only solution, to reinstall my application completely with linstallbuilder. When I run my jar in command line it works perfectly, para, if I run it via the binary generated by installbuilder I get a certificate error. So I updated the jdk and jre (1.8.0.121 which supports let's encrypt) on the mac. The let's encrypt root certificate is present only on the latest java versions. My java application calls a webservice in https, since this weekend i have changed the ssl certificate for a certificate let's encrypt. I noticed that on OSX the java updates are not supported for install applications with install builder. Then I could run the autoupdater app in with separate update.ini files to check for updates for all our products.Īny chance this possible, or could be made available if it's not currently possible? The rest of the info (where to find downloads, current version of product (versionID), which update.xml to look at on server, etc.) is all outside the autoupdater app, which is cool and does what I need. That way our autoupdater app could simply be named "REVision Effects AutoUpdater" (our company name), and then the product name in the dialog box(es) could be displayed based on what's in the update.ini file instead of having it built into the autoupdater app. My question: What I'd like to do is create one auto-updater, and use the update.ini file for each product to specify the product name that appears in autoupdater program, instead of having to put the product name in an autoupdater.xml file that is used to build the autoupdater program(s). And many of those 37 products are supported on Mac, Win and Linux. I'm working with eval version of InstallBuilder and want to make a script that checks for all of our products in one go, one update check for each of our 37 products (okay, just the products that are installed on the customer's computer, but you get the point). We are a plug-in company that has 37 or so installers. The Folder found and loaded the file fine (apparently NOT case-sensitive), but unpackFile could not find it until I renamed the file in the Windows file system to Filename.dat (removed the camel case). The file name in the Windows system was FileName.dat. The issue turned out to be unpackFile is case-sensitive. I have several instances of this scenario in the code and only 1 was failing. Below is pseudo code of what is in my project. I'm using the Windows version of the InstallBuilder Pro. I checked the component, folder and file names in the installer project and all were correct. I thought this was rather strange since to build the installer the file had to exist. When using unpackFile I was getting an error indicating that it could not find the file to unpack. Not all aspects of InstallBuilder are case-sensitive, so it gets confusing when you run into a scenario where one command is case-sensitive and another isn't. This isn't really a question, just wanted to share a case-sensitivity issue I ran across.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |