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.
Summary: | Need a way to force restart on plugin reactivation | ||
---|---|---|---|
Product: | platform | Reporter: | venkatramakkineni <venkatramakkineni> |
Component: | Module System | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | venkatramakkineni |
Priority: | P4 | ||
Version: | 7.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 206036 | ||
Bug Blocks: |
Description
venkatramakkineni
2011-12-19 05:23:36 UTC
*** Bug 206517 has been marked as a duplicate of this bug. *** Consider using http://bits.netbeans.org/dev/javadoc/org-openide-awt/org/openide/awt/NotificationDisplayer.html to show a notification and http://bits.netbeans.org/dev/javadoc/org-openide-util/org/openide/LifecycleManager.html#markForRestart() to restart. When would I call mark for restart. How to recognize when the plugin has been activated ? I have tried using restored method in the Installer, but this method is called everytime the plugin is loaded on netbeans startup. Putting markForRestart in the restored method will make netbeans to go into an infinite restart loop. When would I call mark for restart. How to recognize when the plugin has been activated ? I have tried using restored method in the Installer, but this method is called everytime the plugin is loaded on netbeans startup. Putting markForRestart in the restored method will make netbeans to go into an infinite restart loop. What about trying to use NbPreferences to record whether your module has been closed or uninstalled? Started for the second time, etc.? But this enhancement depended on was resolved. This may mean the enhancement is not needed anymore. Jaroslav I found the solution was a workaround and not a straight forward way to mark for restart on plugin reactivation. I learned that this is by design as Netbeans team is trying to reduce the number of restarts. But, for LNF related plugins, restarting seems to be the only way. Another reason I closed the bug is because while they rejected my 7.1 version, they somehow accepted the 7.2 version. Possibly because saubrecht has a LNF plugin released for 7.2 and 7.3 and that plugin has a similar problem and his plugin passed verification. I opened this bug when Netbeans verification team rejected my verification 7.1 version. Now that the plugin passed verification, I don't have a use for this feature. Your suggestions .. |