Hey,
when trying to update the jme3 sdk (via help->check for updates) I get the following error message:
“Check your network connection, verify that your proxy settings are configured correctly, or try again later.”
Regularly I get the following error (In the bottom right corner, where the sdk also informs about updates):
java.lang.NoClassDefFoundError: org/netbeans/updater/XMLUtil
at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogParser.newEntityResolver(AutoupdateCatalogParser.java:114)
at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogParser.(AutoupdateCatalogParser.java:83)
at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogParser.getUpdateItems(AutoupdateCatalogParser.java:179)
at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogProvider.getUpdateItems(AutoupdateCatalogProvider.java:143)
at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogProvider.getContentDescription(AutoupdateCatalogProvider.java:121)
at org.netbeans.modules.autoupdate.services.UpdateUnitProviderImpl.getContentDescription(UpdateUnitProviderImpl.java:137)
at org.netbeans.api.autoupdate.UpdateUnitProvider.getContentDescription(UpdateUnitProvider.java:146)
at org.netbeans.modules.autoupdate.ui.actions.CheckForUpdatesProviderImpl.getContentDescription(CheckForUpdatesProviderImpl.java:106)
at org.netbeans.core.ui.ProductInformationPanel.getUpdates(ProductInformationPanel.java:397)
at org.netbeans.core.ui.ProductInformationPanel.access$000(ProductInformationPanel.java:81)
at org.netbeans.core.ui.ProductInformationPanel$1.run(ProductInformationPanel.java:121)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1452)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2032)
My network connection works just fine! I’m using SDK 3.0RC2 and “1.7.0_17; Java HotSpot™ 64-Bit Server VM 23.7-b01” is installed.
My System: Windows 7 version 6.1 running on amd64; Cp1252; en_US
Reinstallation leaded to working updates at first. After the usual restart of the sdk after an update, the error and the update failure reappeared.
Greetings