log4p

Over a year ago I tried working with the maven2 plugin for eclipse. After trying some of the nifty features, like a search dialog for dependencies, I was totally fed up by the amount of resources needed by the plugin; every tiny move you made seemed to trigger full maven build cycles (including update checking in online repositories)… which made it impossible to work with.

I decided to stay as far away from the plugin as possible… until I recently noticed Howard Lewis Ship (author of the excellent Tapestry framework and Hivemind) using the plugin while demonstrating tapestry 5. If Howard is using the plugin (he is running it on OsX by the way), it might have improved I figured.

wrong.

After configuring the plugin on all modules of my current project misery began; the plugin is an enormous resource hog! Each time something happens which triggers rebuilding the workspace (i.e. run project > clean) the entire build cycle is executed… taking about 2 minutes to complete.

Sure, it is possible to run the plugin in offline modus… which makes it a bit faster. But this totally defeats the purpose.

I’ll probably be sticking to executing maven commands using my CLI for the next comming year!