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.
The use case is that user has a somewhat developed project with mixed use of multiple frameworks one of them REST. Later it is decided to rearchitect REST beans to a separate project. Manually removing libraries, servlet adaptor, deployment descriptor changes and project meta files is too cumbersome and error prone. To support framework removal, we need change in web/webapi, something like: WebFrameworkProvider { void unextend(WebModule wm); } Also, Web project customizer Framework panel also need a 'Remove' button.
I think that removing frameworks we shouldn't support through in the IDE. I don't see your use case as relevant. Why user should decide to remove a framework? If we allow this, then after the removing the bulk of projects will be uncompilable and IDE shouldn't do such operation.
What if somebody chooses some framework by accident? Or after a while chooses to use alternative support for say the Spring framework. If the users can add support for more frameworks at any time they will expect they can also remove it. I know there are technical difficulties with removing certain frameworks, so maybe this functionality should be optional. In any case the users should be warned when adding support for non-removable frameworks so that they think twice if they really need it.
Petr, I think that my use case for removing framework during rework on architect, is valid. As development grow larger, there could be need to split classes by one framework to a separate project and leave the current project free from that framework artifacts.
I'm not still convinced that we need this functionality. If we will do that I can imagine many P2 issues like "I remove the framework and now I'm not able to build the project". I haven't heard such request from a user, always from testers and some developers, who writes a framework support. Probably you are right, so it can be done in this way: I will add a method void remove(WebModule) (unextend is nice, but I didn't find such word in a dictionary :)), with default implementation, which will just display a message like "This framework doesn't support Removing operation.".
remove(WebModule wm) is fine. For framework that does not support remove, I think for better UI flow, we needs another method canRemove(WebModule wm) instead of dialog message.
I agree. Your suggestion is right.
*** Issue 72498 has been marked as a duplicate of this issue. ***
See also: http://www.netbeans.org/issues/show_bug.cgi?id=109051 Requests on the nbusers forum: http://www.netbeans.org/servlets/BrowseList?list=nbusers&by=thread&from=804759 http://www.netbeans.org/servlets/BrowseList?list=nbusers&by=thread&from=377675 http://www.netbeans.org/servlets/BrowseList?list=nbusers&by=thread&from=811381 http://www.netbeans.org/servlets/BrowseList?list=nbusers&by=thread&from=487699
In Visual Web Project>Project Properties their is a "Add" button available to add frameworks under the "Frameworks" category. Suppose if i accidentally added a framework and pressed "ok" button and i come around next time to the project properties to remove that framework their is NO "Remove" button available to remove that framework. Don't you think their should be one to "Remove" as well as adding frameworks.
I believe the fix/enhancement should start from the top web project API, and then passing down to each framework for updating. I.e., currently, there is nothing visual web can do/implement to start the 'remove' functionality/UI.
I too would like to be able to remove a framework from a project. So what if it doesn't build afterwards. If you are using libraries that are no longer being referenced by the project, that is what you would expect to happen. The problem that I'm running into is that I was running NetBeans 5.5 and was using JSF 1.1. I upgraded to 6.1. Now it says "The selected Java EE version does not support the selected Java Server Faces version." I want to revert back to JSF 1.1 because my app needs to run in Java 5 and Tomcat 5.5 which installed separately. Now, it looks like I'll have to recreate the project unless I can figure out what config files I need to modify.