Hi Rob, How do I use the old server view in trunk? I wanted access it to compare and highlight missing useful things in the new server view, such as https://jira.jboss.org/jira/browse/JBIDE-3096 And what about my status suggestion? I think it's important that status is showed. Here's what I suggested to your email a couple of months back: "Why not put State and Status as something like Modules...etc? Something that is expanded by the server. In fact, you could probably have a single line for them two, i.e: JBoss 4.2 Server |-> Status: Stopped/Synchronized |-> Modules..." Cheers,

So, how do I know that you're missing something else from the old view? Do you expect me to keep another oldish version of JBDS and compare? Rob Stryker wrote: > The old has been removed from trunk. I know this probably wasn't the > best thing to do right away but I had a reason, and it is still in > the beta1 release. The reason I removed it so quickly is that I've > got big changes coming in a general sense and a significant portion > of the classes in AS Tools are being changed in a limited amount of > time. Many are being removed outright as I try to streamline the > code. Having a legacy view using old classes would make it difficult > for me to trim the fat effectively without trying to maintain two > views for each commit. > > Galder Zamarreno wrote: >> Hi Rob, >> >> How do I use the old server view in trunk? I wanted access it to >> compare and highlight missing useful things in the new server view, >> such as https://jira.jboss.org/jira/browse/JBIDE-3096 >> >> And what about my status suggestion? I think it's important that >> status is showed. Here's what I suggested to your email a couple of >> months back: >> >> "Why not put State and Status as something like Modules...etc? >> Something that is expanded by the server. In fact, you could >> probably have a single line for them two, i.e: >> >> JBoss 4.2 Server >> |-> Status: Stopped/Synchronized >> |-> Modules..." >> >> Cheers, >