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.
With 8.0RC1 imported settings from 7.4. After NB startup, there was a info box that asked if I wanted to import plugins from previous release; click'd yes. Dialog came up with some plugins, selected all the plugins, click YES (or install or something like that) NOTE: At least one of the plugins required a restart on install Observe that the plugins are all activated and NB does NOT restart. In my case the editor became unusable (some of the plugins were for jVi). Expected a restart. (manual restart and things are OK)
Could you please attach messages.log files ? Thanks in advance.
Created attachment 145841 [details] log file
In the attached log, note that the module org.netbeans.modules.jvi/0 [1.5.19.30 131127] is turned on. (I've changed the priority since this bug could easily cause data corruption) In Info/info.xml from org-netbeans-modules-jvi.nbm (from its release) there is: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//NetBeans//DTD Autoupdate Module Info 2.5//EN" "http://www.netbeans.org/dtds/autoupdate-info-2_5.dtd"> <module codenamebase="org.netbeans.modules.jvi" distribution="" downloadsize="0" homepage="http://jvi.sourceforge.net/" license="20824F0F" moduleauthor="Ernie Rael" needsrestart="true" <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< releasedate="2013/11/26">
Ernie, the import of plugins offers two different ways how to import plugins from previous installation: first, the plugin importer searches for plugins on Update Centers. If it did not find them there, then imports the plugins (i.e. copying plugins jars) directly (if all other dependencies are matched). Back to your case, iVi plugin was found in previous installation, that's the reason why iVi was subject of import. iVi hasn't been published on any 8.0 Update Center yet, it means iVi cannot be install via NBM, so no NBM's metadata will be read. The Plugin importer had to choose the way copying the jars directly, without restart. Hope it makes sense.
I understand what's happening, it makes sense. But that doesn't mean it's not a bug. It is crashing part of NetBeans, the editor in this case. It could be fixed, for example by keeping more plugin metadata around. Or by always restarting if some imported NBM is not available. I am reopening because it is a bug (IMO), so WORKSFORME is inappropriate. Close as WONTFIX and I'll make no further comment. PS... The jVi Update Center, one of the plugins, is awaiting validation for 8.0. The jVi modules are loaded through this update center. I'm wondering, if the jVi UC is in the 3rd party UC, will the plugin importer first load the jVi UC and then load the NBMs? (At least for jVi this would avoid the bug)
(In reply to err from comment #5) > Close as WONTFIX and I'll make no further comment. Or, we can tracking this as an enhancement. Perhaps some volunteer could take care of it. > PS... > The jVi Update Center, one of the plugins, is awaiting validation for 8.0. > The jVi modules are loaded through this update center. I'm wondering, > if the jVi UC is in the 3rd party UC, > will the plugin importer first load the jVi UC Yes, it will be (except if an user is offline). > and then load the NBMs? (At least for jVi this > would avoid the bug) Right, it should. Regards, Jiri