In the project preferences it is possible to configure a lifecycle mapping. But for some reason I can only add custom goals to “after clean” and “on resource changed”. When I add the “compile” goal to the “resource changed” lifecycle mapping, then the JavaScript files are compiled when I change a resource. So I could put my JavaScript files into the resources folder instead and it would work but this sounds pretty ugly.
As you’ve noticed, the default goals run on incremental builds in Eclipse are process-resources and resources:testResources. Personally, I don’t find ugly to put js file under resources and I would just bind the javascript plugin on process-resources.
It is also working when I tell Eclipse to “clean” my project. Then the compile goal target is called.
On full build (after a clean from Eclipse), goals run are process-test-resources which is actually a build lifecycle phase that includes the compile phase, that’s why compile get called when you clean your project from Eclipse. But this doesn’t solve your issue (running your plugin on save).
As I said, I would just put the js file under resources. But there is maybe another option: adding another Builder to the project. Right-click on your project, then Properties > Builders > New > Maven Build and define your plugin goal as goal to run during Auto Build Goals (change or remove the other goals to suit your needs):
alt text http://img694.imageshack.us/img694/2382/screenshot003wo.png
But I prefer the other approach.