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.
After installing python using the python installer on top of the NB 6.5 installation, uninstalled the python model from Plugins Manager to re-install a newer build. However, the python installer indicated that all modules have been installed so it's no longer possible to re-install python again with a new build to the same NB 6.5 installation. Workaround: uninstall NB 6.5 and reinstall it before installing python again.
The issue is that we have no integration between Plugins Manager and Installer (see Issue 54182). The same issue will be most probably happen with ruby, c++ and other feature-per-cluster things. From the other side, if user is running (un)installer and the overall cluster is missing, then, I agree, installer should catch that situation and then allow using to installer the feature again. That should be an easy-fix, really. We just need to override validateInstallation() method for NbClusterConfigurationLogic.java where we need to iterate over clusters (clusterNames) and checking for their existance. If _neither_ exist then the feature can be treated as the uninstalled one. Yulia, wanna fix this one ? :) The only questionable thing is what to do if some clusters are missing and some are not for the specific pack (e.g. for Java Web & EE pack). We can consider 2 options - either treat at still installed or treat as broken and thus mark it as not-installed and thus suggest to (re)install it. Or we can just ask user to make a choice :) Something like "repair" functionality is missing... For now my opinion is to keep it as "installed" and do nothing. Peter, thanks for reporting! Really good issue.
It is not so easy to fix this bug due to different install/uninstall algorithms for UC and installer. During installation/uninstallation of the particular cluster (i.e. php) UC add/remove some staff from another clusters (gsf, ide, etc) according to modules dependencies. Whereas installer doesn't check/analyse any modules dependencies and just extracts cluster dir (i.e. php1) to the installation location. As a result, if cluster has been uninstalled by UC it can't be re-installed by installer since installer doesn't know which files were removed by UC from the other clusters so these files will be missed. The bug will be fixed as soon as Issue #54182 is fixed. *** This issue has been marked as a duplicate of 54182 ***