IntelliJ IDEA vs Eclipse: Core Concepts, Project Settings, and Essential IDE Tips
This guide compares IntelliJ IDEA and Eclipse, explains the workspace shift, walks through default and project-specific configurations for JDK, Maven, Git, Tomcat, and presents a collection of practical shortcuts and UI tweaks to boost Java development productivity.
IntelliJ IDEA is presented as a modern, intelligent development tool compared with the older Eclipse, highlighting the shift from a workspace‑centric model to IDEA's project‑and‑module structure, which allows each module its own JDK and Maven settings.
1. Core terminology comparison – IDEA treats Project and Module as separate concepts, eliminating the need for a global workspace. This flexibility is a key advantage over Eclipse.
2. Current project configuration vs default configuration – IDEA provides a "Default Settings" (now "Default Settings /ProjectStructs") for new projects, while each project can still have its own JDK, Maven, and other settings. The article shows how to open both configurations via File → Other Settings → Default Settings /ProjectStructs and File → Settings /ProjectStructs .
3. Global JDK (default configuration) – Set the global JDK through File → Other Settings → Default Project Structure → SDKs → JDK and apply it to individual modules as needed.
4. Global Maven (default configuration) – Configure Maven via File → Other Settings → Default Settings → Build & Tools → Maven , preferably using a user‑specific settings.xml and specifying a local repository to avoid data loss.
5. Version control (Git/SVN) – Enable Git/SVN support in File → Other Settings → Default Settings → Version Control → Git , set the executable path, and test the connection.
6. Auto‑import and smart removal – Activate automatic import handling via File → Other Settings → Default Settings → Auto Import to keep imports tidy.
7. Tomcat server configuration (project‑specific) – Add a Tomcat application server under File → Settings → Deployment → Application Servers → Tomcat Server and configure deployment settings.
8. Automatic compilation – Enable auto‑make in the Registry ( compiler.automake.allow.when.app.running ) and use Ctrl+Shift+F9 for hot‑swap updates.
9. Disable case‑sensitive completion – Set File | Settings | Editor | General | Code Completion Case | Sensitive Completion = None for more comprehensive suggestions.
10. Font and appearance – Adjust editor font type and size via the Font settings to improve readability.
11. Keymap matching Eclipse – Switch the keymap to Eclipse under File → Settings → Keymap → Eclipse for familiar shortcuts.
12. Show toolbar – Enable the toolbar and tool buttons via View → Toolbar & Tool Buttons .
13. Handy shortcuts – Examples include middle‑mouse‑button for intention actions, F2 to rename, F3 to reveal in Explorer, and Ctrl+Mouse Right‑Click to navigate to implementations.
14. Additional tweaks for power users – Disable case sensitivity, hide IDE configuration directories (.idea, .iml), and collapse documentation comments via Code Folding settings.
15. FAQ – Answers common questions such as opening existing projects, closing projects, handling multiple Maven modules, adding new modules, and more.
The article concludes with a "(完)" marker and a promotional QR code for the author’s Java content.
Java Captain
Focused on Java technologies: SSM, the Spring ecosystem, microservices, MySQL, MyCat, clustering, distributed systems, middleware, Linux, networking, multithreading; occasionally covers DevOps tools like Jenkins, Nexus, Docker, ELK; shares practical tech insights and is dedicated to full‑stack Java development.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.