Guys, firsthand, thanks for picking up and embracing support for m2, it's gonna be really helpful for many ;)
There's one feature I'd like to discuss. We at Mule have complex m2 project (minimum 70 modules). Why minimum? Because some modules would be part of the reactor only if a certain profile activated (e.g. -Pdistributions for various end-user packaging modules, -Ptests for integration tests, etc.). Take a look at the root pom: http://svn.codehaus.org/mule/trunk/mule/pom.xml
However, when importing a maven project into IDEA (b6981), there's no way to specify a profile. Disable deep scan, it's gonna mess up things due to poms in the examples (have to be manually unchecked for import, which is a pain in a huge project like that).
So, I would suggest one more wizard screen before the Finish, one containing a list of available profiles (or just a text field to enter one for now) and properties key/value pairs (that's another way to activate/disable a profile). Having specified those, m2 would be able to resolve extra modules in the reactor.
Does it make sense? Not sure if you employ m2 embedder to resolve those or scan poms manually.