IntelliJ IDEA: Integrated Team Environment
TS-5033

The story of IntelliJ IDEA evolution has always been a story of how the developers at JetBrains have made their own development life easier. Whatever feature was added--a tiny enhancement or an entire integration with another other tool--it was added for their own productivity purposes. IntelliJ IDEA is an ideal tool that ultimately supports the coding process or, in other words, covers almost every need of a single developer. But does project development end with just coding? Different types of builds and tests, continuous integration, code analysis, version control management, deployment, and maintenance--these are all irreplaceable parts of a project development process. And the developers at JetBrains are also facing the same problems at those stages as all other developers do.

• Automation
• Tight tools integration
• Test/analysis frequency and precision
• Server-side inspections and coverage
• Seamless collaboration

• A build grid that provides leverage for multiple-project load; enables more coverage, inspections, duplicates analysis, and the like; and guarantees more-accurate validation through the use of more installed hardware.
• Delayed commits to version control, where you don't need to worry about whether your last commit before leaving home could break the build; the system replaces the standard Edit--Commit--Verify scenario with Edit--Verify--Commit, which ensures that the version in VCS is always clean and running. Moreover, it is you who decides what clean means: whether the code just compiles or unit tests are also passed, or maybe the new functionality is well covered and code inspection reports no problems.
• IDE integration that allows you to keep working in your friendly environment without any workflow interruptions, so that you can view build logs, monitor currently running tests, or review change diffs directly in IDE, with the opportunity to explore failure stack traces, navigate to failed tests with a single keystroke, obtain estimation for your changes to be tested, and fully control task priorities.
• Teamwork support with code-aware instant messaging and the ability to organize remote code reviews, avoid conflict merges, exchange files with no VCS involved, share IDE configuration, and code style and inspection settings.

Because the environment uses open protocols and a variety of client UIs and supports industry-standard configurations, version control systems, issue tracking tools, and so on, it guarantees that there won't be any vendor lock-in (not to say that it is IDE-independent).

With painless setup and maintenance, the TeamServer is going to become an ideal Integrated Team Environment ensuring productivity increases.

Watch The Session
You need to be a registered Sun Developer Network member to view this multimedia session. If you are a registered SDN member, please click on "Watch Multimedia" button to log-in to view the multimedia session. If you wish to join SDN, please click here.