It is not planned to allow to remove the framework if it was added. The reason
is that if the framework is used in jsp files, these files should stop working.
The project would become inconsistent and not working. All files in project
would have to be scanned if they use the framework before removing it.
If you added the framework accidentally and you are sure that you don't use the
framework, you can remove it by removing framework libraries and framework
configuration file from the project.

I'd vote reconsider support to also remove Frameworks. Since more and more frameworks are being added to nb it is likely
that I just want to try out a framework, to see if it suits my requirements, eg. jmaki support and I was pretty upset
that there was no oppertunity to remove the framework support again and I had to remove all dependencies on my own,
which was quite a job to do!

There could be just an alert telling the user the problems related to 'removeing framework support'. Every framework
provider could be made in charge of scanning source files for dependencies, thus displaying those dependencies some view.

And it's not really a problem if the user decides to remove framework support anyway, since if he can add again anyway
with no unresolved dependensies. But if I just want to try out a framework I'm busted, since I have to investigate by
myselve where the framework provide put all it's dependencies into.

sorry for so many typos (should have checked b4 submitting :))

See also: http://www.netbeans.org/issues/show_bug.cgi?id=109051

This seems to be the same issue that is being discussed at issue 98884. Since 98884 has more info, I am closing this as
a duplicate of 98884. To the submitter: Please reopen this bug if you feel the two are not duplicates.

*** This issue has been marked as a duplicate of 98884 ***