You're right; MyEclipse needs to stop putting stuff in, and fix some of the outstanding problems (deploying issues with Maven springs to mind), but the application server support is pretty great.
Regarding Jetty, you don't actually have to use WTP to do that. You can launch it as an embedded server using the regular "Run As" functionality within Eclipse. The hot deployment of code works quite well, though I'm not sure how it would handle dependent projects. There is a pretty good blog post about it here: http://www.codecommit.com/blog/java/so-long-wtp-embedded-jetty-for-me Mike Robert Voliva wrote: > > We have many projects (but two is a simple example) - and if even a jsp > page is changed, WTP with Tomcat tries to rebuild the entire application > (dependent jars and all). > > We're *evaluating* whether switching to Eclipse is a viable option for > us. Eclipse seems to be more stable - MyEclipse seems to be more > inundated with bloat lately - but the managed deploy works much nicer > than WTP does. > > We talked about using Jetty, but Eclipse doesn't have a Jetty server > adapter for download through the "Install New Server Adapter" interface > - and it's my understanding that the app servers that appear in this > list are ones that have been marked as working with WTP. > ----- -- Michael Laccetti (416)558-9718 S2G Limited http://www.s2g.ca/ -- View this message in context: http://www.nabble.com/Success-with-app-servers-in-Eclipse-WTP---Hot-Deploy-tp16974770p17022842.html Sent from the ivy-user mailing list archive at Nabble.com.
