> J�rgen Jatzkowski writes: > > Hi, ... > Paul Kinnucan writes: > > No. However, you should be aware that JDEbug is of alpha quality. > It has not received much attention over the last two years because > JDE users seemed more interested in other things like Ant support, > hierarchical projects, and field and method completion. > > I am now starting to devote most of my time to debugger support > so the situation should improve. My first priority is to provide > solid support for jdb because jdb is a more mature, though less > capable, debugger. I then plan to work on JDEbug.
I was wondering what % of people here use jdb vs JDEBug (not that I would want my personal preference to JDEBug to affect your priorities). JDEBug, even with some the quirks, was the main reason I started using JDE as a "full-circle" development environment, apart from using emacs to edit Java files. I am glad the debugging environment will improve. Are there some features of your "near-future" jdb changes that will affect JDEBug immediately as well? (I am guessing auto-save of break point could be one, but that's just a guess) Thanks, Milan > > What this means is that I probably won't fix JDEbugs immediately. > > Of course, others can feel free to pitch in and help with JDEbug > if they have the time and inclination. > > > Oops: I'm using Blackdown's JDK 1.3.1 on Mandrake 8.1 (glibc 2.2) > > - Paul
