jMonkeyEngine / sdk

The jMonkeyEngine3 Software Development Kit based on Netbeans
BSD 3-Clause "New" or "Revised" License
314 stars 101 forks source link

Installer just exits after "Next" button is used #486

Closed devent closed 1 year ago

devent commented 1 year ago

I wanted to try the new pre-release v3.6-stable-sdk2 but the installer just exits right after the first welcome dialog shows and I click "Next". Strangely it also prints no error and the exit code is 0. I have already JME SDK 3.5 installed on my computer.

Linux xx-X705UD 5.4.0-144-generic #161-Ubuntu SMP Fri Feb 3 14:49:04 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true openjdk version "17.0.6" 2023-01-17 OpenJDK Runtime Environment (build 17.0.6+10-Ubuntu-0ubuntu120.04.1) OpenJDK 64-Bit Server VM (build 17.0.6+10-Ubuntu-0ubuntu120.04.1, mixed mode, sharing)

Full log log.txt

[2023-03-30 16:04:16.656]: NameResolver - to parse resource:org/mycompany/installer/wizard/components/panels/resources/welcome-left-top.png
[2023-03-30 16:04:16.680]: NameResolver - to parse resource:org/mycompany/installer/wizard/components/panels/resources/welcome-left-bottom.png
[2023-03-30 16:04:16.761]: NameResolver - to parse &Help!
[2023-03-30 16:04:16.765]: NameResolver - to parse < &Back
[2023-03-30 16:04:16.779]: NameResolver - to parse &Next >
[2023-03-30 16:04:16.780]: NameResolver - to parse Cancel
[2023-03-30 16:04:16.851]: NameResolver - to parse <html><h1>Welcome to the jMonkeyEngine SDK Installer Wizard</h1><br>This program will install the jMonkeyEngine SDK on your computer.<br><br>Click Next to continue.
[2023-03-30 16:04:16.903]: NameResolver - to parse jMonkeyEngine SDK
[2023-03-30 16:04:28.333]: entering -- org.netbeans.installer.wizard.components.actions.FinalizeRegistryAction.execute():46
[2023-03-30 16:04:28.333]: finalizing product registry
[2023-03-30 16:04:28.334]:     ... removing remaining installation data for all the products
[2023-03-30 16:04:28.334]:     ... save local registry if necessary
[2023-03-30 16:04:28.334]:     ... save registry to file /home/devent/.jmonkeyplatform-installer/registry.xml
[2023-03-30 16:04:28.334]:     entering -- org.netbeans.installer.product.Registry.finalizeRegistry():329
[2023-03-30 16:04:28.334]:     saving product registry file
[2023-03-30 16:04:28.335]:         ... getting registry document
[2023-03-30 16:04:28.369]:         ... saving registry document to file /home/devent/.jmonkeyplatform-installer/registry.xml
[2023-03-30 16:04:28.369]:         entering -- org.netbeans.installer.product.Registry.saveProductRegistry():1007
[2023-03-30 16:04:28.369]:         saving document to xml file : /home/devent/.jmonkeyplatform-installer/registry.xml
[2023-03-30 16:04:28.577]:         ... document saved
[2023-03-30 16:04:28.577]:         exiting -- org.netbeans.installer.product.Registry.saveProductRegistry():1007
[2023-03-30 16:04:28.577]:         ... saving XML file succesfully finished
[2023-03-30 16:04:28.577]:     ... saving product registry done
[2023-03-30 16:04:28.578]:     exiting -- org.netbeans.installer.product.Registry.finalizeRegistry():329
[2023-03-30 16:04:28.578]:     ... save state file if necessary
[2023-03-30 16:04:28.578]: finalizing product registry
[2023-03-30 16:04:28.578]: exiting -- org.netbeans.installer.wizard.components.actions.FinalizeRegistryAction.execute():46
[2023-03-30 16:04:29]> ... java process finished with code 0
[2023-03-30 16:04:29]> Removing directory /tmp/.nbi-4030359.tmp
[2023-03-30 16:04:29]> exitCode = 0
neph1 commented 1 year ago

Unsure about this, but can you try to remove (or rename to retain config) the .jmonkeyplatform folder and try again? This is in any case necessary to get it to run later. The folder is usually located in your 'home' directory

devent commented 1 year ago

Renaming the folder .jmonkeyplatform helped, the installer works now, thank you. I think you need to improve here. Update the files in .jmonkeyplatform/ to a new version or delete them, or something.

neph1 commented 1 year ago

This release was a special case(?), and it's usually not required to do that. I should have mentioned it in the release notes (I'll go and do that now).