[jbosside-issues] [JBoss JIRA] Commented: (JBIDE-287) Can't view/edit debug configurations with Eclipse 3.2M5

[ http://jira.jboss.com/jira/browse/JBIDE-287?page=comments#action_12352381 ] Michael Bauer commented on JBIDE-287: ------------------------------------- I find this last statement depressing for several reasons: 1) 2.0 is still beta. Its been non-GA for a long time now. Eclipse 3.2, on the other hand, has been around for a long time. In fact, its been around so long that IBM has even integrated 3.2 into the latest RAD 7 release. IBM is not notoriously a "road-runner" when it comes to getting new stuff out. 2) There are a lot of people that have come to depend on the utter simplicity that was in the pre-2.0 version. I, like many other I suppose, only need something to allow me to easily start/stop a JBoss instance and attach to it with the debugger. 2.0 seems to want you to create JBoss projects and such...this is just too much! I don't need Hibernate integration...I do this using Spring. I don't need AOP, since again I do this in Spring. I just need something to aid in debugging my app on JBoss 3) 2.0 seems WAY to complicated. I have tried to get it to work several times, but there is just too much to it. Add to that the fact I can't seem to find any documentation on the main site, and its utterly impossible to figure out. It took me 2 days and several posts to figure out I needed to make a JBoss Inc server not just a JBoss server, and after I actually got the instance running I still couldn't figure out how to "Add Projects" so my breakpoints worked. In the pre-2.0 days, I just opened the Servers tab, added a JBoss server, and told it which project(s) contained my source. Simple enough a child could do it. 4) The fix, from what I read, doesn't sound complicated. I mean, from the impression I got, its like 1 or 2 lines to change the name of the class. I used to use the fix with the 1.5 release that required you to replace the JAR, but that seems to not work in 1.6. I have been using JBossIDE for a long time now, but I believe I will have to stop using it if I can't get it to do what I needed. And I don't need any fancy bells and whistles, either. I just need a start/stop button and the ability to break the code. For now, I guess I will just have to start it manually in "debug" mode and attach remotely via Eclipse. This does not allow me to debug deployment, however, which is a bummer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira