Maintaining Common Project Configuration in a Mixed-IDE Team
When you are working in a team that uses different IDEs, keeping project configuration in sync between team members is very complicated task. Sometimes it can be so cumbersome that you may want to stop trying to put them all together and resort to sharing Ant scripts as the repository for project configurations.
With IntelliJ IDEA 7 (Selena), you can export, import and synchronize IntelliJ IDEA and Eclipse projects.
To import existing EcIipse projects to IntelliJ IDEA:
- Open the File menu, select Import from Eclipse
- Select whether you want a New project or import to the Current project
- If you selected to create the new project, walk through the wizard steps
- Specify the Eclipse projects you want to import (each Eclipse project is converted to a separate IntelliJ IDEA module)
- Select the Link option for all specified projects if you want them automatically synchronized between IntelliJ IDEA and Eclipse and click Finish
Note that if the option is cleared, the one-time import operation is performed and no future synchronization is done.
In case you want to export an IntelliJ IDEA project to Eclipse, open the File menu and select Export to Eclipse. Selecting the Link option keeps Eclipse project file automatically synchronized with IntelliJ IDEA.
You can also convert the arbitrary IntelliJ IDEA project module to an Eclipse-compatible format by adjusting the module settings.
Open the Project Structure dialog, click Dependencies tab and select the appropriate storage format.
This table shows the mapping between some Eclipse and IntelliJ IDEA concepts:
|A number of projects
Named entities are converted to the entities with the same names. If imported Eclipse projects refer to user libraries or classpath variables that do not exist in IntelliJ IDEA project, IntelliJ IDEA will prompt to create them.
As of yet some limitations apply to migrating projects between IntelliJ IDEA and Eclipse:
- IntelliJ IDEA modules with multiple content roots are not migrated
- External sources in Eclipse are not migrated
- Only Java modules created automatically when importing. However, any module can be converted to Eclipse
compatible format manually
- Default workspace JRE is not converted to/from Project JDK
Subscribe to Blog updates
Java Best Practices
Good code follows certain rules, and knowing them increases your chances of success. We’d like to share some Java best practices that will help you on your way. We'll cover the must-know tips and tricks, from broad advice on software development to Java- and project-specific know-how. Let's get star…
The Best of IntelliJ IDEA’s HTTP Client
In today's fast-paced tech world, easy and efficient management of web services and APIs is crucial. That's where IntelliJ IDEA's HTTP Client steps in, turning complex HTTP requests into a walk in the park. The HTTP Client is a feature-rich, text-based tool in IntelliJ IDEA Ultimate. It seamlessl…
Profile Java and Kotlin Code with the IntelliJ Profiler
At JetBrains, we believe that profiling Java and Kotlin code should be simple and accessible to all developers, regardless of their level of expertise. That’s why the IntelliJ Profiler puts ease of use and seamless integration at the forefront of its mission. In previous releases, we introduced a r…
History of Gradle Delegation Process in IntelliJ IDEA
Nowadays, a build tool is an essential part of any project, and IntelliJ IDEA integrates with the majority of them. Among the most popular build tools is Gradle. We’d like to give a brief historical overview of its integration with IntelliJ IDEA and the delegation process implemented inside the I…