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.
Probably not out of nothing, but in any case I know nothing about removing any server out of my web app, that has so far worked fine with Glassfish. Suddenly, errors shown up, like "package javax.servlet.http does not exist", and a menu entry to a dialog "Remove missing server problem". The dialog just wants me to install Glassfish under some directory of choice, which I do not want, because Glassfish is supposedly within Netbeans. It might be because of two installations of NB that share a common SVN repository, and use the repository to fight for whatever reason over their private project files, but anyway, why should it end with an ususable project? Is not using a repository from multiple places a normal thing? Anyway, I suggest to put some relocatable information to these configuration files about Glassfish, so that one instance of NB can understane another instance of NB, that the built--in Glassfish server should be used. Or, simply enable a reconnection of the project with that built--in server, instead of asking the user about downloading another copy of Glassfish. Or, could you at least tell me, what should I do now with the broken project? Thanks.
It turns out, that just restarting NB helps here, so it is only some temporary issue. Perhaps NB should refresh a whole project configuration, if some of the files within nbproject/ change, but I guess it does not have anything to do with Glassfish.
Missing server problem happens when you have project connected with some Glassfish and you delete or replace this server in Services tab. You can just select new GF dependency for your project. This could happen after NetBeans upgrade which could also upgrade your GlassFish. Netbeans usually store config information into separate directories for individual version. You can also face issues when you run more than one NetBeans of the same version at the same time. If you do so, try to run 2nd netbeans with --userdir pointing outside your home directory to avoid conflicts for the future. Please close this bug if your problem is already solved.