The Java Development Environment for Emacs (JDEE) is an add on sotware package for Emacs that assists in the development of software in the Java Programming Language. JDEE provides many Emacs commands that help with the editing, compiling, running, debugging, and browsing large Java programs.
JDEE is freely available under the GNU Public License.See the introductory section of the JDEE User's Guidefor a quick tour of the JDEE's capabilities (an older JDEE Quick Tour is also available).
To use JDEE requires the following software:
GNU Emacs version 23.4 or later.
A Java Development environment. JDEE is know to work with the Oracle JDK and the OpenJDK platforms.
Any Web browser supported by the Emacs browse-url interface for viewing documentation (this includes Firefox, Safari, Internet Explorer and many others).
To download JDEE, visit the project download area. See the JDEE release notes for a description of the changes included in the production release.
You can also get the latest development sources for JDEE from JDEE's Subversion repository. Use the code in the repository at your own risk. It may or may not work depending on the state of development at the time you checked out the code!
See Installing the JDEE for information on installing the JDEE on a Unix or Windows system.
The JDEE distribution includes the JDEE User's Guide. You can also get help via the Emacs M-x apropos and Ctl-h commands.
See Contributed Software for a list of additional tools contributed by JDEE users that you can download from this site.
JDEE has some known major limitations. Being a volunteer driven project these limitations can only be removed by some one committed enough to fix them. Here are the biggest ones you should be aware of
JDEE depends on the BeanShell when looking up details about Java objects. Unfortunately BeanShell does not support generics. Yes, we know it is 2013. Help us fix this!
The JDEE parser is unable to recognize static import statements. It will decide that these statements are not required and if asked to delete unneeded imports it will remove them!
You will be surprised at how usable the JDEE software is even with these limitations.
The JDEE mailing lists provides a technical support, design, and news forum for JDEE. If you are having problems setting up or using the JDEE, would like to propose and discuss enhancements, or simply be advised of the latest JDEE developments, this is the place to turn. Subscription and archives are available from the Sourceforge Mailing List page.
Bug fix notices posted to the JDEE mailing list may instruct you to download patched files from the JDEE's Subversion repository. Use the code in the repository at your own risk. It may or may not work depending on the state of development at the time you checked out the code!
If you have a problem with the JDEE, first check the JDEE Troubleshooting Guide. If you still have a problem running the JDEE, please send your problem report to the JDEE mailing list.
When requesting help, it is important that you provide a complete, detailed description of the problem, and also the Emacs environment in which it occurs. Please include information about
The host platform (e.g., Linux, Mac OS X, Windows, etc.)
The JDEE version (e.g., JDEE 2.4.1)
The Emacs version (e.g., GNU Emacs 23.4.1)
The JDK you are using (e.g., Oracle JDK 1.6.0_26-b03)
complete contents of your .emacs file.
Note Please do not make the common mistake of sending only the so-called "JDEE-related" part of an .emacs file. Send the entire file! If you don't like doing this, trim the file to the smallest amount that allows you to reproduce the problem.
Contents of the backtrace buffer if an error occurs.
To get a backtrace, you can set the Lisp variable
debug-on-error to t before
the error occurs. If you don't know how to do this in Emacs
Lisp, please use the Options -> Enter Debugger on
Error menu item to enable it for the current Emacs
session. If the problem occurs during startup, rerun Emacs,
using the -debug-init command line switch.
Contents of the *messages* buffer immediately
after the error occurred.
Contents of the *JDEEbug* buffer if you are having problems
with JDEEbug
Contents of the prj.el file for the project in which the
problem occurred.
The JDEE includes a JDE->Help->Submit Problem Report command that creates a complete snapshot of your system. If the error occurs after the JDEE is loaded, you can use this command to generate all the information you need to include in the problem report.
Paul Kinnucan graduated from MIT in 1970. In the sixties and seventies, he developed numerical and astronomical image processing software for mainframes at the University of Chicago and MIT. In the 1980s, he wrote about computers, factories, aircraft, and spacecraft for various U.S. trade and general-circulation publications. Recently, he has divided his time between software development and technical documentation. He is currently principal technical writer at The MathWorks, Inc, a producer of engineering math and simulation software. He is responsible for documenting the company's simulation software and developing tools for displaying online documentation for MathWorks products. He has a wife (Fran), son (Michael, age 19), and daughter (Emma, 17). He lives with his family in Milton, a suburb of Boston.
®Java is a registered trademark of Oracle, Inc.