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.
Summary: | Deploy menu item is confusing (M10) | ||
---|---|---|---|
Product: | javaee | Reporter: | arungupta <arungupta> |
Component: | Code | Assignee: | Sherold Dev <sherold> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | bleonard, pjiricka, ppisl, sherold |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 96977 | ||
Bug Blocks: |
Description
arungupta
2007-07-03 20:02:18 UTC
Another option is to find out if the project has been already deployed and change the menu item label accordingly. This has been widely discussed as part of one of issues (sorry I don't have its number by hand) - anyway there was a conclusion that using "Undeploy and Deploy" is better description of the action than "Redeploy". Pavel, I'm sure you know more about this, since you were coordinating this change - can I ask you to take care of this issue, please? Thanks. See http://blogs.sun.com/arungupta/entry/netbeans_6_m10_and_web for more details. see also issue 106616 (where it was decided to use "Undeploy and Deploy"), according to that issue I would suggest to close this issue as WONTFIX Petr and Stepan will give you details. I only made a suggestion to them which they used, they make the decision :-) Issue 106616 does not talk about the meaning of "Undeploy and Deploy" target for the first deployment of project. This does not make sense in that case because the project has not been deployed. I think it's more confusing to have "Undeploy and Deploy". Issue 106616 does not talk about the meaning of "Undeploy and Deploy" target for the first deployment of project. This does not make sense in that case because the project has not been deployed. I think it's more confusing to have "Undeploy and Deploy". The "Undeploy and Deploy" action does exactly what you would expect it to do in case that the project has not been deployed, it simply skips the undeployment step. There are no plans to make the action smarter and change its label based on whether the project is deployed or not. I guess what you are looking for is an action which does plain deploy, see the "Run" action. I was just demoing web services to a customer and we crossed this issue. The problem is that I want to deploy, not undeploy, that's why the menu item is very confusing. How about using: Deploy (with undeploy) Or something similar. Changing dynamically the title whether the project was already deployed or not is not basically possible due to the performance issue. Find out, whether a project is already deployed is time consuming action (especially if the server is not started yet). You can not rely on remembering whether the action was already invoked. You should take care about persisting and about switching target server. In previous versions users complains that they are looking for an Undeploy action, before they do Deploy again. So after a discussion we decide to changed it in the current state. If you now better title for this action, please suggest. How about two menu items "Deploy" and "Undeploy and Deploy" ? How about two menu items "Deploy" and "Undeploy and Deploy" ? Issue 106616 says "this was decided" but not by whom. I guess it was on nbusability or somewhere else where I didn't see it. Not to reopen the discussion, but how about simply "Deploy / Redeploy" or "Deploy (Redeploy)" AND make sure that the F1 help for the action indicates exactly what this action will do and in what cases (e.g. under what circumstances it will do a full undeploy, and whatever else happens). There's a limit to how much of the underlying plumbing we can describe inline and still have a usable menu item. I suspect that more users will be confused by this new terminology than were confused by the old one. I like "Deploy (Redeploy)". F1 help can explain that Redeploy means Undeploy and Deploy. I think there is no need for an explicit Undeploy menu item. I like "Deploy (Redeploy)". F1 help can explain that Redeploy means Undeploy and Deploy. I think there is no need for an explicit Undeploy menu item. There is issue #96977 which is assigned to me. As you can read in the issue, this issue is a part of a complex problem. I would like to solve it ASAP, but now there are issues with bigger priority. I'm open to the discussion how it should be solved. websvc module is not the best place for this issue, moving to j2ee since it applies to all Java EE project types Closing as WONTFIX, what needs to be fixed is issue 96977. |