This issue is transferred from bugtraq (4621993).
Customer should be able to uninstall a module if module becomes corrupt or is
affecting other functionality. In addition customer should be able to reinstall
the module in question.
A partial solution could be to add an additional state (or flag) to a disabled
module so when user access the update center the user can then download and
install the flagged (corrupt) module.
Jesse, what do you think about this suggested partial solution?
The flagging thing sounds like very strange UI, I am not sure what the
purpose is. Better to just permit direct deletion.
Suggest a pure abstract class in org.netbeans.core.modules that would
delete a module though it be a scanned module. ModuleNode could look
for such a thing in lookup and make scanned module nodes deletable
using it, if present.
However that would be a hack. Prefer to wait for Looks to make it
possible to set an "AutoUpdate look" on the ModuleNode, which would
handle deletion of tracked modules, as well as the NewType for NBMs.
See Radiance case Case ID: 62836648 Task ID: 64641095:
"how to cleanly uninstall / rollback to the previous version, the
SOAP TPM module"
This is particularly an issue with Tech. Preview Modules, which are
beta overwrites of the fcs modules (ex: webservices.jar)
Marking as duplicate of #20323, which is more complex.
*** This issue has been marked as a duplicate of 20323 ***
Verified - duplicate.
Resolved for 3.3.x or earlier, no new info since then -> closing.