Not according to the UI spec.

Assigning to jrojcek for more evaluation.  If the UI spec changes,
please note it and reassign the issue for fixing.

ok, there were differences in ejb/web/j2ee modules...I thought that
web module action was named according to UI spec....now web and ejb
modules have both Deploy action.
btw, nor Deploy neither Redeploy are clear in their meaning.

All the specs now say Deploy.

Ok, so now we have two items: "Run" and "Deploy".

Everything I know about the difference between "Run" and "Redeploy" is
contained in this by Pavel:

http://www.netbeans.org/servlets/ReadMsg?msgId=888021&listName=nbj2ee

So, I am assuming that the difference between "Run" and "Deploy" is
still as described in Pavel's message, i.e., that "Run" takes the
minimal steps needed for running an app (i.e., moving only the changed
files to the server) while "Deploy" undeploys and then redeploys the
application.

If the above distinction is correct, then that is something we can
explain in the docs. However, it is still not very intuitive. Someone
looking at "Run" and "Deploy" is not automatically going to understand
the difference (for most people, these two verbs are synonyms).

But Pavel was speaking about web project. For EJB there is no
difference between Run and Deploy.

Okay, I will put here my perspective on how those actions work (should work?) for all 
project types:

Web Run - does "incremental" deploy and opens the main web page in a browser
Web Deploy - does undeploy then deploy and doesn't open any web page in a browser

EJB Run - does "incremental" deploy
EJB Deploy - does undeploy then deploy

EntApp Run - does "incremental" deploy and opens the main web page in a browser
EntApp Run - does undeploy then deploy and doesn't open any web page in a browser

Is this how it works? If not, somebody please summarize the actual behavior of Run/
Deploy for all projects.

Jano - did you mean this?

EntApp Deploy - does undeploy then deploy and doesn't open any web
page in a browser

Web and EJB project do not follow the UI spec (they have "Redeploy"),
assigning to Andrei.

Yes, I meant "EntApp Deploy" as the last item.

The web and EJB project don't follow the UI spec because Pavel Buzek
said it should be Redeploy. Assigning to him.

BTW I don't think "Run" is a good name for "incremental deploy". We
probably shouldn't have "Run" in the EJB project at all, because this
action doesn't "run" anything, it merely deploys the EJB module to the
server. I understand we want to be coherent (since we have "Run" in
the web project). But should we give an action a rather undescriptive
name just to be coherent?

IMO in the EJB project we should have: 
- "Deploy" (for the incremental deployment, if it works) with shortcut F6
- "Redeploy"

I think in the web project we could have the same, i.e., "Deploy" and
"Redeploy" instead of "Run" and "Redeploy". But I'm not sure what
should happen if a project hasn't been deployed yet. If it hasn't been
deployed yet, maybe the "Redeploy" should be disabled? Of course, I
don't know about all the reasoning that are behind these decisions, so
this is just an uninformed opinion.

FYI, WSAD5.1 has only 'Run on server' and 'Debug on server' choices
and is satisfied with this. From my own experience it is enough for a
user.

Maybe we should shift to higher level of abstraction. The user usually
wants to _run_ (or debug) his module without differing between
deploy-run and deploy/redeploy.
He simply wants to see the result and he is not interested in details
like incremental deploy.

With Deploy operation we has to solve to problem with EJB module -
does a user want to run server in debug mode or not?

Yes, but my understanding of the difference between 'Run' and 'Deploy'
is that one is FASTER than the other. One is incremental and the other
undeploys everything and then redeploys everything. So maybe the menu
items should reflect this distinction somehow (e.g., "Quick Deploy"
and "Complete Deploy").

We have to stick with Run, because there is "Run Main Project" menu item and "Run" is the 
contextual alternative of that action. We can maybe call it "Undeploy and Run" or 
"Undeploy then Run" or something like that, which looks a bit weird.

If I understand correctly the conclusion is that I will rename the menu item on
web application project from Redeploy to Deploy. This action will undeploy the
web module if previously deployed and then deploy it. I will also make sure that
this action does NOT bring up the browser, which is filed as 51599.
This can be easilly fixed in 4.1.

doing a real undeploy, then a deploy make sense, so yes...
Are we doing the same on ejbmodule and j2ee apps? I am not so sure anymore...

I checked in the source of ear and ejbjar projects and yes, we are doing
undeploy/deploy on the deploy action. This is what Jano recommended here.
(it is _not_ what is in UI spec, btw)

I checked in the source of ear and ejbjar projects and yes, we are doing
undeploy/deploy on the deploy action. This is what Jano recommended here.
(it is _not_ what is in UI spec, btw)

fixed in web/project, ear, ejbproject:

cvs commit -m "55312 Deploy/Redeploy action"
src\org\netbeans\modules\web\project\ui\Bundle.properties (in directory
C:\nb_all\web\project\)
Checking in src/org/netbeans/modules/web/project/ui/Bundle.properties;
/cvs/web/project/src/org/netbeans/modules/web/project/ui/Bundle.properties,v 
<--  Bundle.properties
new revision: 1.32; previous revision: 1.31
done

cvs commit -m "56522 Clean&Build\n55312 Deploy/Redeploy action"
ejbjarproject\src\org\netbeans\modules\j2ee\ejbjarproject\ui\Bundle.properties
utilities\src\org\netbeans\modules\j2ee\common\ui\Bundle.properties (in
directory C:\nb_all\j2ee\)
Checking in
ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/ui/Bundle.properties;
/cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/ui/Bundle.properties,v
 <--  Bundle.properties
new revision: 1.10; previous revision: 1.9
done
Checking in utilities/src/org/netbeans/modules/j2ee/common/ui/Bundle.properties;
/cvs/j2ee/utilities/src/org/netbeans/modules/j2ee/common/ui/Bundle.properties,v
 <--  Bundle.properties
new revision: 1.6; previous revision: 1.5
done

Verified.