I never had a fully functional install of JDEE, so I won't compare it to eclipse. Configuring JDEE itself gave me nightmares. From what I remember, I would se

I never had a fully functional install of JDEE, so I won't compare it to eclipse. Configuring JDEE itself gave me nightmares. From what I remember, I would set variables to the proper VM and experience no change. At the time I gave up on JDEE I had the opportunity to switch to Python and I never looked back at Java. I think JDEE suffers from being too large with too many dependencies. Emacs configurations make almost every install unique and I think the maintainers of emacs projects in general have a hard time supporting users because people generally stop writing documentation when "It works for me." The same way you find your keys in the last place you look. For instance http://jdee.sourceforge.net/install.html http://jdee.sourceforge.net/install.html Download the latest versions of Eric Ludlam's speedbar, eieio, and semantic bovinator packages and install them on your system, each in their own directory. You can download these packages from SourceForge. Note Emacs and XEmacs include earlier versions of speedbar that are incompatible with the JDEE. You must delete the earlier version or ensure that it is not on the Emacs load path. Otherwise you will get a Lisp error when trying to start Emacs. That documentation might have made sense at the time. but I'm currently using emacs 23.3.1. Is my version of speedbar still out of date? Do I have to downgrade it? Upgrade it? http://cedet.sourceforge.net/ http://cedet.sourceforge.net/ The cedet page for getting those "newer" packages only provides download links to the entire cedet package. And without version references in the documentation how can I tell if my debian installed version might be good enough?