This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I've already tried to delete var/cache and var/filehistory, didn't help. A similar bug has been reported by review, but only against running in target platform (forgot the id, sorry).
Created attachment 61883 [details] The log file
Could you please start NB with fresh user dir? http://wiki.netbeans.org/DevFaqUserDir
No. Won't delete my settings, doesn't seem helpful. The problem seems to be caused by missing this: org.apache.xalan.processor.TransformerFactoryImpl not found Probably there's some code depending on JDK 1.4? I've found the xalan classes included within JDK 1.4.2, but not in 1.5 or 1.6 ...
Hmm, just found this in the log file: WARNUNG [org.netbeans.ProxyClassLoader]: Will not load class org.apache.xalan.processor.TransformerFactoryImpl arbitrarily from one of org.netbeans.StandardModule$OneModuleClassLoader@1cc7f4b[com.eviware.soapui.netbeans.module] and org.netbeans.StandardModule$OneModuleClassLoader@1264bf5[com.jaspersoft.ireport] Seems to be a module/classloader conflict. Should be resolved with the module owners. Setting priotity to P2 - it still should have high priority, as these modules are available from the plugin center and have been featured by netbeans, but IMO module issues are usually no showstoppers (although very anoying).
Shouldn't only say, I'll go to decrease prio ;-)
As the module problem arised after update: Did probably sth. change in handling of modules and/or libs? BTW: Can I change/remove *only* the opened editor settings, without deleting any installed modules, project properties etc.? I've added several project groups, modules and other settings I don't want to loose.
none of these modules is developed by netbeans team. Jirko, can we somehow pass it to plugin owners ? 1, com.eviware.soapui.netbeans.module 2, com.jaspersoft.ireport >As the module problem arised after update what update do you mean? The project groups, editor setting etc. are stored in <nb_user_dir>/config directory. If you copy particular settings to new userdir manually then it should work.
*** Issue 135920 has been marked as a duplicate of this issue. ***
>>As the module problem arised after update >what update do you mean? I've had the same modules installed before the update, and it worked. So it might be classloader issue or related. On the other hand, it would probably be easier to find the problem's cause, if I could at least see the NB GUI. But the IDE starts up (yes, I can see about 250MB used by a java process in the win task mgr, so the second phase of starting NB has [nearly] finished) without showing any GUI, nor does the task icon appear (I'm thinking about the thing You see using ALT+TAB). Probably I should add the zipped user NB user dir (or, better, send it directly to You)?
Hi, the log indicates that you are not using the latest version of the soapUI NetBeans module, could you please make sure that you are actually using the one available from the update center (in the Tools\soapUI\About soapUI Plug-in it should say Build Date 2008/04/18 11:04)? regards! /Ole eviware.com
I've removed the jars for soapui and ireport, then I could start NB with GUI. Removed also the keytools plugin (because of a suspicious messgae about user.ks, which hasn't existed in var/cache/catalogcache). I had also to remove var/cache and var/filehistory again. After restarting, the auto update came to life ... and now I can work again. Probably there's been some hangup in the autoupdate module (probably because of some bad modue install?), so the bad thing is, there's now GUI appearing, which tells about that, and work seems to stop there. Probably somebody could improve this? At least, the IDE (or whatever part of it is running) should have a GUI telling about the problems and allowing to shut down NetBeans while also disabling corrupt updates.
Closing as worksforme.Feel free to reopen if reproducible again.