It seems to work in FoD builds, so feel free to close this issue if it's not reproducible for you. Anyway, downgrading 
to P3.

The framework should go away, since that one is specified in the project module, which seems goes away.

However you are right, that there are other visual web modules, which still stay around. It seems it is too complex
issue, and it needs to be correctly resolved following the autoupdate spec.

I've spent some time already with that, it seems it is very time consuming.
Since there is a plan to move the modules to autoupdate anyway, I'll postpone this until there is a time left for that.

I added missing AutoUpdate-Show-In-Client flags to the module manifests, also added missing dependencies to
visualweb.kit module (see the changeset).
However it still seems to not work, and a lot of modules (no all) are getting loaded after unistalling of the visualweb.kit.

I pass this to autoupdate temporarily.
Please, could there be a problem in autoupdate? It seems I added all dependencies to the visualweb.kit module, made all
of the modules to be AutoUpdate-Show-In-Client: false, and some of them still get loaded.

Also how could I debug the module loading? I.e. I would need to find out why particular module (which has
AutoUpdate-Show-In-Client: false) got loaded (whether there is some some missed dependency or so).
Thanks.

changeset:   111509:7ff03b2515e5
tag:         tip
user:        Peter Zavadsky <pzavadsky@netbeans.org>
date:        Fri Dec 12 12:52:13 2008 -0800
summary:     #153839 Trying to fix the loading of modules after uninstalling the kit module.

please attach ~/.netbeans/<version>/var/log/messages.log* files.

Please note that module loading is out of control of AU - it is the functionality of the module system.
Having AutoUpdate-Show-In-Client flag set to false means that this module will not be visible in the Plugin Manager.
It has no effect on whether the module is loaded or not.

Integrated into 'main-golden', will be available in build *200812131401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/7ff03b2515e5
User: Peter Zavadsky <pzavadsky@netbeans.org>
Log: #153839 Trying to fix the loading of modules after uninstalling the kit module.
It still seems to not fully work.

Created attachment 74976 [details]
Log of 1st start when uninstalling visualweb.kit

Created attachment 74977 [details]
Log of 2nd start (restart) after unistalling visualweb.kit, still lot of visualweb modules present

I attached the logs:
1) messages.log.1  - log after 1st start (clean userdir) and unistalling of visualweb.kit (the kit module for visual web),
2) messages.log - log after restart, the visualweb.kit module got unistalled, also some other visualweb modules, but
still a lot of visualweb modules got loaded.

As I understand the deal with the autoupdate visibility and loading, I assume that module shouldn't be loaded when its
kit module is not loaded and there is no non-kit module which depends on such module.
That should be true for all of the visualweb modules, but they still get loaded. I can't detect which, non-visualweb
module keeps them loaded, or whether it is an issue of the module loading, or whether I missed something with the kit
module functionality.

I bump up the priority, because this seems to be breaking the assumed functionality for us. Also, please, assign it to
the appropriate module, if that belongs somewhere else. Thanks.

I really doubt that visualweb.kit can be a friend of any other module.
What is the purpose for doing that? 

I speak about the following line(s) added in the changeset #7ff03b2515e5:
<friend>org.netbeans.modules.visualweb.kit</friend>

From the other side, I can`t say for sure whether having this line can cause this issue or not.

I added the kit module as a friend to some of the visualweb modules, so the kit module can depend on them, in order to
force their uninstall when unistalling the kit itself.
Those modules don't have public API's, so there is no other way to depend on them, only via friend dependency.

I am checking if all those modules have indirect dependencies to kit module via some other modules having public API's.

OK, it seems all those modules, the kit has friend dependency on, have indirect dependency on kit anyway, so I am gonna
remove those.

Removed the friend deps (see the changeset). However it still seem not to help, still the modules get loaded, even they
have direct or indirect deps on the kit module only, which gets uninstalled.
Those modules should get uninstalled as well, but they do not, from unknown reasons.

changeset:   112104:c04efd533f4f
tag:         tip
user:        Peter Zavadsky <pzavadsky@netbeans.org>
date:        Wed Dec 17 11:05:18 2008 -0800
summary:     #153839 Removing redundant friend dependencies.

The friend dependencies shouldn't matter, otherwise one wouldn't be able to add such module into kit, unless it depends
on some public module (which is not always the case).

Integrated into 'main-golden', will be available in build *200812221122* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/c04efd533f4f
User: Peter Zavadsky <pzavadsky@netbeans.org>
Log: #153839 Removing redundant friend dependencies.

In fact, deactivation of Visual JSF deactivates only the following modules/kits:
org-netbeans-modules-visualweb-complib
org-netbeans-modules-visualweb-dataconnectivity-designtime
org-netbeans-modules-visualweb-dataprovider-designtime
org-netbeans-modules-visualweb-ejb
org-netbeans-modules-visualweb-errorhandler-client
org-netbeans-modules-visualweb-j2ee14classloaderprovider
org-netbeans-modules-visualweb-j2ee15classloaderprovider
org-netbeans-modules-visualweb-jsfsupport-designtime
org-netbeans-modules-visualweb-jsfsupport-designtime_1_1
org-netbeans-modules-visualweb-jsfsupport-designtime_1_2
org-netbeans-modules-visualweb-kit
org-netbeans-modules-visualweb-palette
org-netbeans-modules-visualweb-project-jsfloader
org-netbeans-modules-visualweb-ravehelp-rave_nbpack
org-netbeans-modules-visualweb-samples-bundled
org-netbeans-modules-visualweb-web-ui-appbase
org-netbeans-modules-visualweb-websvcmgr
org-netbeans-modules-visualweb-webui-jsf-defaulttheme
org-netbeans-modules-visualweb-webui-themes

I`m continue investigations.

I can`t say that for sure but it looks like something wrong with visualweb.gravy module.

First, some facts (if I got them correctly):
1) It is invisible module
2) It is autoload module
3) It is not included in any of the visible kit(s)
4) It is included in the nb.cluster.visualweb
5) OpenIDE-Module-Display-Category=Testing Tools
6) If I remove visualweb.gravy from nb.cluster.visualweb then deactivation of Visual JSF works pretty fine.
7) It depends on a bunch of other visualweb modules (visualweb.{dataconnectivity,designer,designer.html, 
designer.jsf,designtime,insync,navigation,outline,xhtml})
8) No other module has the module-dependency on this module, only test-dependency

Jesse, Jirka, is it a valid module configuration?

If it is only used in tests, and we have no reason to ship it, probably it can just be removed from the visualweb
cluster. But I don't know why it would be causing any problems if it is indeed autoload.

Since visualweb was moved to UC, it is not ncluded in any existing standard distributions. 
Due to that and all other facts, gravy will not be present on the system when user installs VisualWeb.
In other words, Visual JSF would be deactivated correctly.
Downgrading the priority to P4 and I`ll investigate it in the future when the time permits.

Who cares?