- This topic has 10 replies, 5 voices, and was last updated 18 years, 12 months ago by
.
-
Posts
-
I remember reading about this issue a long time ago, and I was glad that it was being worked on. But this is 1 or 2 years ago, and nothing has happended. The problem is this:
It is very inconvenient to restart my Tomcat with the dropdown buttons provided by MyEclipse. You have to click, move the mouse on a small area (I usually click the wrong button by mistake every second time) down to tomcat, and click once more to stop the server. And then repeat the procedure for starting the server. The sysdeo plugin does this much better, with a single click for restarting.
Is this not something that MyEclipse users want and ask for?
I also would like to “see” whether my server is running or not. Just a small traffic light widget next to the restart button would be ideal, or perhaps just disable the restart button when the server isn’t running.
I now frequently hit the stop button out of habbit, only to get an exception (from tomcat, in the console) stating the server couldn’t be stopped since it’s not running.
I like the way WTP and its derivatives handle starting & stopping servers: a drop-down to choose the server and separate buttons to start, stop & restart. Will the 4.1 release be modeled this way?
Sorry to keep harping on this, but the recently released 4.1M1 looks like a pretty good improvement (still not quite all I’d like, but definitely an improvement). Considering it’ll probably be awhile before 4.1GA, any chance we could see a backport of this feature with the next 4.0.x release? <please, please, oh, please> 😀
Eric
Eric,
We are glad to hear it’s getting closer to what you want. Can you be more specific about additional changes you would like to see? (describing exactly the behaviors)And no to the backport, sorry, but 4.1 should be out in December. I know it seems a long way away, but we have Thanksgiving comming up, then you will be shopping for Christmas and by the time you are done, you will have a newsletter in your inbox from us saying 4.1 is out 😉
The only thing I think is missing is the ability to easily stop the server. As I said before, I think the WTP is very friendly in this regard, at least for me, since I do the bulk of my development on one server configuration. It’s almost always one-click start/stop/restart. Also, regarding arjan.tijms’ request, the enabled state of the buttons lets you see if the server is running or not. But I would say the “memory” for starts and restarts is 2/3 of the way there (and I would think over time you would be migrating towards leveraging WTP, so eventually you’ll be 3/3 of the way there).
As far as the backport goes, I was imagining the 4.1GA would be in the spring sometime. You guys must really be cranking away!
Thanks for listening
EricEric,
I have a better idea of what you want here and we will naturally get some of this as we pull in portions of WTP that make sense, so let’s leave what we have now until 5.0 and then pick that conversation up again when the underpinnings are changing.As far as the backport goes, I was imagining the 4.1GA would be in the spring sometime. You guys must really be cranking away!
Oh you can’t believe it, the productivity is insane. Multiple times a week I end up with more screenshots, examples or emails in my inbox describing new features like autocomplete all over the place, drag and drop bean creation for Spring, etc. etc. Across the board the team is just meshing so well and our output is really screaming. We hope to get some down time over Christmas/New Year, but come the new year we will be back at it.
There are times when the automatic deployment cannot complete. This means that I need to do a re-deploy on the project to a server. No problem, I understand the causes.
However, it would be nice if the deploy icon showed the current deployment state. Say green for “Successfully Deployed”, red for not? I have started the server, only to get errors because the automatic deployment failed.
Maybe this should be a separate entry, sorry about the thread jack ….
