January 17, 2006

Not installing IDEA plugins properly can have weird side-effects

In the last few versions IDEA has created and refined a plugin manager, so generally you just need to click a couple times and it grabs the plugin, and installs it to the right place. It works well for me.

Recently I installed the IdeaSpring plugin. Same procedure as above, and everything seemed to work well. But then I noticed weird GUI behavior in two areas: the 'Go To' dropdown menu didn't work, and right-clicking folders in the project view didn't work. (I didn't notice the first for a while because most of the things I do are hardwired into my fingers, so I don't need the menu.) This seemed to happen only with projects that are built against JDK 1.3, but I'm not entirely sure about that.

Looking in my ~/.IntelliJIdea50/config/plugins directory quickly showed why: a README.txt there said to copy the idea-spring-parser.jar into IDEA's lib/ directory. So I assume the reason the menu items were failing was an IdeaSpring callback that threw an exception. And that things worked in JDK 1.4+ projects because of the built-in XML parsing functionality.

What concerns me is this mix of automated and manual installs: the graphical plugin manager works but apparently there are some plugins that require extra configuration -- not that I would ever know this from the installation process. To the plugin author's credit, there is an ALL CAPS NOTE in the changelog that you have to do the library copy. But who reads the changelog when they're installing for the first time?

Next: Two updates on the Steeler game
Previous: del.icio.us feeds not updating?