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.
Like Eclipse's plugin - http://code.google.com/p/run-jetty-run/ It can run the maven project with jetty and scan its local maven dependency project, if you are working with multi-projects. The benefit is that it doesn't need to run the war:war phase and automatically redeploy when another local maven dependency changed and all the jobs can be done in a second.
if it's just about associating mvn jetty:run with the Run action, that should be easily achievable by editing the project properties, actions panel.
No, the actions panel cannot detect the dependency project's change, unless you have to put all the stuff in the pom.xml, but if the project is edited by a lot of developers and it cannot be hard-code in the pom.xml, that means each developer has their own dependency, which needs to be scanned by jetty server. I had tried a lot of way to solve this, but so far I can do is to use jetty:run with the current project, and use terminal to run with rsync to sync another maven projects to the current maven classpath, which is not efficient. That is why we cannot make a decision to move from Eclipse to NetBeans. I also checked with NetBeans's source code, it seems that have a way to check if there depend on some of the local dependency projects, and then the NetBeans's IDE should be able to add the dependency scanner for jetty server. Sorry for that I am not a NetBeans's plugin expert, I cannot do this by myself.
By the way, if you means the "Build With Dependencies", it will package each dependencies as a jar and then run with the current war project, that will spend 30~40 seconds in my SSD hard-disk, not like Run-Jetty-Run in a second.
*** This bug has been marked as a duplicate of bug 243484 ***