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.
Product Version: NetBeans 6 IDE Dev (Build beta1: 200709270000) System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06 Steps: 1. Installed Java SE (not EE) 2. Used plugin manager to add Visual JSF and Tomcat plugin (restart IDE) 3. Created a EE5 project to verify functionality was properly added 4. Uninstalled Visual JSF plugin (restart IDE) 5. File New > Web > Visuale Web JavaServer Faces framework is still available on the wizard When I press finish It creates a very broken project (needs resolving).
Created attachment 49762 [details] plugin manager after uninstalling Visual web.
Correction: I was using 200709280000, not 0927.
Jiri, it looks like the uninstall of a kit module is broken. In this example, the kit module is 'Visual JSF'. Is this a known issue?
I found one problem in visualweb/kit module. It should contain dependency to visualweb/xhtml module because this module causes visualweb/project/jsf and visualweb/jsfsupport. Add visualweb/xhtml module among other dependencies of visualweb/kit. In general, if Visual JSF kit depends on (a kit) Java Server Faces then Java Server Faces cannot depends on Visual JSF. It means installation of Visual JSF forces installation Java Server Faces and uninstallation Visual JSF don't. Uninstallation of Java Server Faces forces uninstallation Visual JSF. If both module needs each other then consider joint both kit into once.
I made and tested the suggested change but it still doesn't uninstall the kit properly. I looked into the JavaServer Faces kit under web/jsf/kit but there is no such dependency on visualweb/xhtml anywhere. Jiri, can you shed some light on this dependency that you stated please?
Created attachment 49940 [details] unsigned locally built visualweb/kit module.
Investigating with some assistance from Jiri.
I undertake the issue to me for now. It needs more investigating in PM.
After fix of issue 117332 it works for me. Only last thing which stays in visualweb cluster after uninstalling Visual JSF is Complib API module. The Complib API pretend as a kit module as Uncategorized but I guess it should be hidden. However, this module doesn't bind any Visual JSF functionality and doesn't make any problem. IMHO I can decrease the priority down (maybe even better file new issue about remaining Complib API I let it up to you).
Complib api should be hidden of course. I noticed several times that new modules are added to build and not hidden. By default when adding a module pls hide it and add to the kit. If, by design, a new module should _not_ be hidden the category must always be Web & Java EE (I will have to rename Web and Java EE to Web & Java EE to match the install page, BTW) and never Visual Web.
Yes, the uninstall of Visual JSF kit appears to be working now. I made the complib api module part of the kit and hidden by default. I also changed the category name of the kit to Web & Java EE as mentioned by Pavel. I don't know if Pavel already in process of changing the category name for other web modules though, so I didn't touch the other web & java ee modules. Checking in complib/api/manifest.mf; /cvs/visualweb/complib/api/manifest.mf,v <-- manifest.mf new revision: 1.3; previous revision: 1.2 done Checking in kit/nbproject/project.xml; /cvs/visualweb/kit/nbproject/project.xml,v <-- project.xml new revision: 1.9; previous revision: 1.8 done Checking in kit/src/org/netbeans/modules/visualweb/kit/Bundle.properties; /cvs/visualweb/kit/src/org/netbeans/modules/visualweb/kit/Bundle.properties,v <-- Bundle.properties new revision: 1.5; previous revision: 1.4 done Jiri, although the Visual JSF kit is not set to be installed globally, it is automatically installed globally now into visualweb1 cluster in the netbeans/ dir. Is this change recent? Do you know what triggers this?