Tue 13 Jun 2006
I’m a jetbrains fan and in particular a long running user of their IntelliJ IDEA Java IDE. I have been flipping between eclipse and intellij for years. The defining moment for me was moving from eclipse 2.1 to intellij 4.x. For me there was no competition. Eclipse simply didn’t cut it for the speed of refactoring and navigability once inside the java editor window.
Of course both IDEs have moved on, IntelliJ to 5.x and Eclipse to 3.x. I am now migrating back to the eclipse platform (project constraints) and its painful. The biggest pain is its lack of support for hiearchical project structures. In other IDEs there is no problem in having projects and subprojects (or modules in IntelliJ), but in eclipse all projects are peers. No parent/child relationships allowed. I find this absolutely nuts! Can someone out there in eclipse land explain why we have this limitation? There must be good reason that I’m just not getting.
When you look at open source projects (e.g. geronimo) that use build tools such as Maven 2, they support hierarchical project structures. Having to fight with eclipse to support common project structures is something we all could do without…
I’ll keep looking!
June 13th, 2006 at 5:09 pm
Do your project constraints force you to use Eclipse IDE or only platform? If you only need its SWT or RCP, you can configure IntelliJ IDEA paths and work with Eclipse platform without problems.
June 13th, 2006 at 5:33 pm
Unfortunately the IDE Alexandra. Although I am interested in your solution. Do you have any more on this by way of example?
July 7th, 2006 at 6:03 pm
I haven’t tried this yet, but it appears you can support hierarchical maven projects within eclipse by flattening out the parent-child relationship. See the end of this doc:
http://maven.apache.org/guides/mini/guide-ide-eclipse.html
July 7th, 2006 at 8:15 pm
Hey merlyn, what these guidelines ask developers to do is work around the shortcomings of eclipse. It would just be nice if eclipse provided support for hierarchical projects. One day eh…
July 10th, 2006 at 3:58 pm
Hmm. From following the posting in their issue tracking system, it really doesn’t sound like they want to change the way Eclipse views projects.