Eclipse is a free, powerful, open-source, and configurable IDE. I recommend you spend some time configuring Eclipse to meet your needs.
<aside> <img src="/icons/light-bulb_gray.svg" alt="/icons/light-bulb_gray.svg" width="40px" /> Try to close projects in Eclipse when you are no longer working on them. This can improve performance and reduce the warnings and TODOs reported to just the projects you are currently working on.
</aside>
TABLE OF CONTENTS
We use the maven tool to setup, compile, and test your projects in this class. You can setup how Eclipse uses Maven in the Eclipse preferences:
In particular, you may want to check the “Download Artifact Javadoc” so Eclipse has local access to the documentation for all the third-party libraries we use and the “Update Maven projects on startup” so you do not need to run that command manually as often.
The homework and project code should not have warnings, including Javadoc warnings. If you want your Eclipse to have similar compiler settings, download the files below:
In the Eclipse Preferences view, click the “Import” button near the bottom left and select the import the eclipse-compiler-settings.epf file. Or, follow these steps to import the epf Eclipse preferences file. Follow the prompts to import the compiler settings.
<aside>
<img src="/icons/warning_gray.svg" alt="/icons/warning_gray.svg" width="40px" /> Note that it is not exactly the same—the autograding feature on GitHub Actions uses the javac compiler and mvn command, whereas Eclipse uses its own built-in Java compiler instead.
</aside>
Your code should have proper Javadoc comments for all members and methods before requesting a code review. To receive warnings when you are missing something (or something is out of date) with your Javadoc comments, use these settings: