Bug 103214 – Actions available in popup menu after module uninstallation

HOME \ Community

Bug 103214 - Actions available in popup menu after module uninstallation

Summary:

Actions available in popup menu after module uninstallation

Status:	VERIFIED FIXED

Product:	versioncontrol
Component:	Code
Version:	6.0
Platform:	All All

Priority:	P3 (vote)
Target Milestone:	6.0
Assigned To:	issues@versioncontrol
QA Contact:	issues@versioncontrol

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-05-03 10:21 by novakm
Modified:	2007-05-29 12:44 (History)

Issue Type:	DEFECT
Exception Reporter :

Attachments
Exception Stacktrace (2.91 KB, text/plain) 2007-05-03 10:22, novakm	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From novakm 2007-05-03 10:21:11

I uninstalled the Mercurial module, but the popup menu invoked on a versioned
project in Projects view was still available. After choosing any action,
follwing exception appeared:

java.io.IOException: Top component hgversioning could not be loaded, either
owni
ng module was disabled, has incompatible version or top components settings
file
 format is broken.
        at
org.netbeans.core.windows.persistence.PersistenceManager.getTopCompon
entPersistentForID(PersistenceManager.java:496)
        at
org.netbeans.core.windows.persistence.PersistenceManager.getTopCompon
entForID(PersistenceManager.java:587)
...

NetBeans IDE 6.0 Preview (M9, build 070502)
1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03
Linux version 2.6.9-1.667 running on i386
en_US (nb); UTF-8

------- Comment #1 From novakm 2007-05-03 10:22:39 -------

Created an attachment (id=42086) [details]
Exception Stacktrace

------- Comment #2 From John Rice 2007-05-03 11:32:51 -------

Will target fix for rev 1.1

We are not doing anything special on uninstall. Is there something we need to
set to make the Versioning framework refresh it's menus?

------- Comment #3 From novakm 2007-05-03 11:54:01 -------

Well I just found out, that other modules (Subversion for instance) behave the
same, so it is not probably caused by your module. It must have changed with
the
new module manager as it worked before I think. I'll try to find out more and
update here as soon as I'll know anything.

------- Comment #4 From Maros Sandor 2007-05-03 12:12:05 -------

I guess this is not a problem of mercurial.

------- Comment #5 From Maros Sandor 2007-05-11 13:03:11 -------

I think that I fixed this lately, please verify in latest builds.

------- Comment #6 From novakm 2007-05-29 12:44:15 -------

Verified.