IntelliJ调试器有一个非常方便的特性，叫做“表达式计算”，这比eclipses pendant好得多。它有完整的代码完成，我认为它通常“更有用”。

Alt+Insert以列模式编辑文本。

其他一些事情:

propagate parameters/exceptions when changing method signature, very handy for updating methods deep inside the call stack SQL code validation in the strings passed as arguments to jdbc calls (and the whole newly bundled language injection stuff) implemented in/overwritten in icons for interfaces & classes (and their methods) and the smart implementation navigation (Ctrl+Alt+Click or Ctrl+Alt+B) linking between the EJB 2.1 interfaces and bean classes (including refactoring support); old one, but still immensely valuable when working on older projects

我认为您可以坚持使用这两个ide中的任何一个。 不要“担心在您没有使用的IDE中错过一个巨大的好处”的最好迹象是我们在Eclipse爱好者和IntelliJ爱好者之间看到的很长的争论。这是一个很好的迹象，双方拥有几乎相同的力量，这使得这场长期的讨论得以幸存。

一个非常有用的特性是能够部分构建Maven反应堆项目，以便只包括您需要的部分。

To make this a little clearer, consider the case of a collection of WAR files with a lot of common resources (e.g. JavaScript, Spring config files etc) being shared between them using the overlay technique. If you are working on some web page (running in Jetty) and want to change some of the overlay code that is held in a separate module then you'd normally expect to have to stop Jetty, run the Maven build, start Jetty again and continue. This is the case with Eclipse and just about every other IDE I've worked with. Not so in IntelliJ. Using the project settings you can define which facet of which module you would like to be included in a background build. Consequently you end up with a process that appears seamless. You make a change to pretty much any code in the project and instantly it is available after you refresh the browser.

非常简洁，而且非常快。

我无法想象在没有它的情况下，在像YUI这样的东西中编写一个返回到DWR/SpringMVC的前端。

Intellij有一个比subversion或Subclipse优秀得多的SVN插件，而且它是有效的!我们在使用Eclipse合并源文件上所浪费的时间是无法想象的。对于IntelliJ，这不是一个问题，因为插件可以帮助你更多。

此外，Subclipse插件也不可靠——我们经常遇到插件认为其他开发人员没有将任何代码签入SVN的情况，但确实存在——CI服务器已经处理了它们!