一个非常有用的特性是能够部分构建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的前端。

就这篇文章而言，我的时机可能有点不对，但我必须做出回应。

我是一个超级日食迷——从它第一次出现就开始使用它。一个朋友告诉我(10多年前)，这将是一个播放器。他是对的。

然而!我刚刚开始使用IntelliJ，如果您还没有见过或使用过变更列表，那么您就错过了编程的天堂。

The ability to track my changed files (on my development branch ala clearcase) was something I was looking for in a plugin for eclipse. Intellij tracks all of your changes for a single commit, extremely easy. You can isolate changed files with custom lists. I use that for configuration files that must be unique locally, but are constantly flagged when I sync or compare against the repository -- listing them under a changelist, I can monitor them, but neatly tuck them away so I can focus on the real additions I am making.

此外，还有一个提交日志插件，可以输出那些没有与错误跟踪软件集成的SCCS的所有更改的文本。将日志粘贴到票据的工作历史记录中可以捕获文件、它们的版本、日期/时间和分支/标记。太酷了。

我打赌，所有这些都可以通过eclipse中的插件(或未来的增强)来支持;然而，Intellij使这变得轻而易举。

最后，我真的很高兴主流对这款产品的喜爱——按键，所以它很痛苦，但很有趣。

我最近发现IntelliJ IDEA与Eclipse相比至少有两个优点。

如果试图在JSP代码编辑器中使用代码格式化，JSP脚本就会出错。Eclipse变得有点疯狂，它到处发布随机的代码片段。IDEA表现得很好。

另一件事是在JBoss服务器上部署应用程序的速度。IntelliJ正在替换JBoss tmp文件夹中的应用程序，因此重新部署非常快。Eclipse WTP正在替换deploy文件夹中的应用程序，而后者的持续时间要长得多。

显示导航栏ALT-Home。

IntelliJ具有从代码到jspx文档的智能感知和重构支持。

一个非常有用的特性是能够部分构建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的前端。