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.
It would be great to have [deploy] menu option available also for maven based projects with war packaging It would be then consistent with the current behavior of regular webapp projects.
dkonecny, phejl: what is the "Deploy" menu item good for when we have "run" which does actually perform a deploy as well? Do we need both? What is the difference?
[Run] will also start the browser, so after re-deploying the app several times you would end-up with several browser tabs open, which is kind of annoying. Another thing is that the thing is a bit counterintuitive. And i still think it is not consistent with what people used to NetBeans would expect.
Afaik the difference is that the deploy is in fact (undeploy & deploy) so it is a bit safer and deploy does not open browser for you.
FYI, unfortunately "Deploy" has also another meaning in maven projects and it's means to upload the project's binaries to a remove repository. That will be the first thing that comes to mind to maven users. Somehow we need to come up with a name that doesn't clash with the maven meaning and still is close to the ant project's deploy notation. Maven projects seem to force the redeploy of the webapp on "Run" by default. Unless configured with execution property named "netbeans.deploy.forceRedeploy" to suppress it. How does Deploy on save feature influence the meaningfulness of running a deploy without undeploy?
Changing the default owner to issues@javaee.
Closing as WONTFIX. During the past 6 years, no-one else ever complained and it doesn't make many sense to include Deploy if it means something else in the context of Maven.