JDEbug vs jdb vs JSwat vs gdb

I've just been reading the archives about JDEbug being in an "alpha"
state.  Before doing that I tried it with CVS Emacs (22) and got it to
work mostly but did run into an Elisp bug that has been reported
(Daniel Flesner, "2.3.5.1 and debug mode" on Jul 24).  After I send
this message off I fully will find out what the issue is with this
bug and see if I can fix it.

I was particularly taken aback to read Paul K's message where he
essentially confessed to little faith in JDEbug.  Assuming jdb and
JDEbug were both bug free (a giant leap, of course) what is the
advantage of JDEbug?  I ask from the perspective of "should I
volunteer time to help make JDEbug work properly or just use jdb and
go with the flow?".  Based on the archives, I will give jdb a try and
see if it meets my needs.  I have a hunch it will.

I must confess that JSwat does not appeal to me if it comes with
NetBeans baggage and overhead.

I've seen no mention of gdb.  I must confess that in my C days I swore
by gdb.  I know that gdb-mode has turned into "GUD" but I don't really
know if that is good, bad or indifferent.

I would also suggest that someone bite another bullet (I may) and fork
JDE into a subversion based repo.  If the fork is a dismal failure
then no sweat.  If it catches on then Paul K will likely be a huge
beneficiary to the extent more hackers can stand on his shoulders and
he will have a vibrant alternative when his life choices leave him
with more time to devote to JDE.

My interest is in seeing Emacs as a Java development environment
continue to grow and develop along with Eclipse, NetBeans, IntelliJ,
etc.  That is only going to happen if one of us, who ostensibly care,
make it happen, being the nature of Open Source.

-pmr