Bug 139052 - Database features are enabled after uninstalling
Database features are enabled after uninstalling
Status: NEW
Product: db
Classification: Unclassified
Component: Code
6.x
All All
: P4 (vote)
: TBD
Assigned To: Libor Fischmeistr
issues@db
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-04 17:04 UTC by Petr Jiricka
Modified: 2013-08-01 12:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2008-07-04 17:04:32 UTC
1. Run the full IDE with a fresh user dir
2. Go to Tools -> Plugins
3. Select the Installed tab, search for 'Database'
4. Select the uninstallation checkbox next to the Database module row and click the Uninstall button
5. Confirm the uninstallation of all the depending modules and restart the IDE as instructed
6. After restart, go to Services tab
=> Database functionality is still there and was not uninstalled

A cue for why this is happening is in: 
http://deadlock.netbeans.org/hudson/job/trunk/lastSuccessfulBuild/artifact/nbbuild/build/generated/kits.txt

Warning: ambiguous module ownership - module org.netbeans.modules.db (ide) is contained in kits 
  org.netbeans.modules.bpel.kit (soa)
  org.netbeans.modules.compapp.kit (soa)
  org.netbeans.modules.db.kit (ide)
  org.netbeans.modules.form.kit (java)
  org.netbeans.modules.glassfish.javaee (j2ee)
  org.netbeans.modules.glassfish.jruby (ruby)
  org.netbeans.modules.hibernate (java)
  org.netbeans.modules.hibernateweb (j2ee)
  org.netbeans.modules.identity.kit (identity)
  org.netbeans.modules.j2ee.jboss4 (j2ee)
  org.netbeans.modules.j2ee.kit (j2ee)
  org.netbeans.modules.j2ee.persistence.kit (java)
  org.netbeans.modules.j2ee.sun.appsrv81 (j2ee)
  org.netbeans.modules.j2ee.weblogic9 (j2ee)
  org.netbeans.modules.j2ee.websphere6 (j2ee)
  org.netbeans.modules.mobility.end2end.kit (mobility)
  org.netbeans.modules.ruby.kit (ruby)
  org.netbeans.modules.soa.kit (soa)
  org.netbeans.modules.tomcat5 (j2ee)
  org.netbeans.modules.visualweb.kit (visualweb)
  org.netbeans.modules.web.jsf.kit (j2ee)
  org.netbeans.modules.web.kit (j2ee)
  org.netbeans.modules.web.struts (j2ee)
  org.netbeans.modules.websvc.kit (j2ee)
  org.netbeans.modules.websvc.restkit (j2ee)
  org.netbeans.modules.xslt.kit (soa)
No dependency between 
  org.netbeans.modules.db.kit (ide), org.netbeans.modules.glassfish.javaee (j2ee)
  org.netbeans.modules.db.kit (ide), org.netbeans.modules.glassfish.jruby (ruby)
  org.netbeans.modules.db.kit (ide), org.netbeans.modules.hibernate (java)
  org.netbeans.modules.db.kit (ide), org.netbeans.modules.hibernateweb (j2ee)
  org.netbeans.modules.db.kit (ide), org.netbeans.modules.ruby.kit (ruby)

I picked the db module as one example of this problem, but I suspect an analogous problem is there for other modules too.
Comment 1 David Vancouvering 2008-07-29 18:41:55 UTC
Is this still happening for you?
Comment 2 David Vancouvering 2008-10-09 18:46:38 UTC
I was able to reproduce this.
Comment 3 Jiri Rechtacek 2009-02-10 15:30:18 UTC
Reassigned to new owner.
Comment 4 Jiri Rechtacek 2010-03-17 12:32:18 UTC
Still reproducible in recent builds.
Comment 5 Jiri Rechtacek 2010-10-18 15:06:14 UTC
It's a valid problem but I think too complicated to fix. The problem is Derby depends on Database Explorer and Glassfish depends on Derby. It means uninstall database (incl. DB Explorer) trying remove Derby, then Glassfish and in the end, Glassfish cannot be uninstalled because too many other modules depends on Glassfish. Fix needs repeating models db.kit, web.kit and j2ee.kit.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo