It's really nice to be able to right-click on a class that has a main method and select "Debug <class>.main()" to run it right away without having to first go through the "edit configurations" dialog, however, in a multi-module project, it's rarely the case for me that the run configuration that is generated for the debugging uses the classpath of the module in which the class resides, so I wind up having to go back to the dialog and say "no, don't use the classpath of that module, use the classpath of this other module". This happens when running / debugging classes that reside in a module-specific library, though I'm not sure that that matters.