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.

Bug 132673 - uml plugin not enable after installed from plugins manager until ide restart
Summary: uml plugin not enable after installed from plugins manager until ide restart
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2008-04-12 01:02 UTC by Peter Lam
Modified: 2008-04-29 16:26 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lam 2008-04-12 01:02:25 UTC
After uninstalling and reinstalling the UML plugin through plugins manager (UC), the installer indicated that the plugin
was installed successfully but it's not enabled. After a manual restart of ide, the uml plugin is enabled.

Scenario #1:
- downloaded the latest RC1 build (full installer) from http://download.netbeans.org/netbeans/6.1/rc/
- customize to install only the base NB without anything else
- install UML plugin from Plugins Manager
- after installation is successful, the UML plugin is enabled as marked with a green check mark
- uninstall the UML plugin
- restart ide from the NB installer dialog to complete the uninstallation 
- install UML plugin from Plugins Manager again
- after installation is successful, the UML plugin is not enabled as marked with a red "x" <<== FAILED to enable
- a manual restart of the ide will enable the plugin

Scenario #2:
- downloaded the latest RC1 build (full installer) from http://download.netbeans.org/netbeans/6.1/rc/
- customize to install only the base NB plus the UML plugin
- start ide
- uninstall the UML plugin
- restart ide from the NB installer dialog to complete the uninstallation 
- install UML plugin from Plugins Manager
- after installation is successful, the UML plugin is not enabled as marked with a red "x" <<== FAILED to enable
- a manual restart of the ide will enable the plugin
Comment 1 Jiri Rechtacek 2008-04-15 17:07:17 UTC
It's reproducible in NB6.1RC1 build. I'm investigating what's wrong...
Comment 2 Jiri Rechtacek 2008-04-16 12:48:42 UTC
I have found the causation of this problem. UML plugin creates new cluster for itself and reads this cluster correctly
for first time. Uninstall of UML _empties_ (but _not removes_) that cluster and module system doesn't uml cluster any
more. For second time installation, Plugin Manager uses uml directory and don't need to create new one cluster. But
module system will read modules from existing cluster unless IDE restart.
It's regression in NB6.1 caused by handling .lastModified files.

Hint for fix: either remove whole cluster if no modules left there or notify module system about new cluster every time,
not only if new one cluster comes up.

Hint for workaround: offer IDE restart if module system doesn't load being installed plugin.
Comment 3 Jiri Rechtacek 2008-04-25 14:40:38 UTC
http://hg.netbeans.org/core-main/rev/299c414c0af5

QA guys, do you think it could be a patch1 candidate? Have in mind it will include update of updater.jar what we haven't
done ever before. Maybe now's the time :-)
Comment 4 Lukas Hasik 2008-04-25 15:02:45 UTC
not in patch1 maybe in patch2. Let's discuss it next week
Comment 5 Quality Engineering 2008-04-26 03:53:36 UTC
Integrated into 'main-golden', available in NB_Trunk_Production #158 build
Changeset: http://hg.netbeans.org/main/rev/299c414c0af5
User: Jiri Rechtacek <jrechtacek@netbeans.org>
Log: #132673: uml plugin not enable after installed from plugins manager until ide restart
Comment 6 Jaromir Uhrik 2008-04-29 08:06:27 UTC
I think it is not a candidate for a patch - the scenario is not very common (users probably uninstall and reinstall a
plugin only seldom).
Comment 7 Peter Lam 2008-04-29 16:26:44 UTC
Correct. This is not a common scenario.