Not sure the testCompile dependency has anything to do with it. It is possible, but Idoubdt it. If you suspect it might, you can try commenting it out and doing the import again. Missing dependencies like that shouldn't cause the import to fail though you might end-up with an incomplete classpath for your project(s) after import, causing compile errors in the workspace.
What seems most likely at this point to me, given where the error is coming from is that its some weirdness caused by names with funny characters.
Not sure how to diagnose it. If I could reproduce it and poke around with a debugger I could probably figure out what's going wrong. But you say you weren't able to reproduce it in a sample project.
One thing we can try is add more info to that error message (e.g. dump the entire contents of computed name mapping in it, maybe it will reveal something interesting about the suspected name 'funnyness').
This will require you to update to a snapshot build of gradle tools and then when you get the error again, we may get a bit more info.
I'll post something here when I got something for you to try later.
Kris De Volder -- SpringSource