Is it my eyes or did you remove the dependency of the module's app
server from the run config?
It used to be that the module was assigned an app server, like a JDK,
and I would need to also setup a run config with the same app server,
anything less would cause idea to just choke.
Now I accidentally created a new run config and chose a different app
server than the one the module was set for and it worked. The module
was set to Tomcat 5.5.9 and the run config was Tomcat 5.0.30. No
If that's the case... pretty cool... if not, then I'll file a bug or
something... or maybe I won't because it's better that way :D