I've run into the same problem.

The release notes from the latest version 1.9-20130911220033+0000 claim that this is solved. Only thing changed seems to be the line number ...

at org.gradle.buildinit.plugins.internal.maven.Maven2Gradle.generateFqn(Maven2Gradle.groovy:213)
at org.gradle.buildinit.plugins.internal.maven.Maven2Gradle.this$2$generateFqn(Maven2Gradle.groovy)
at org.gradle.buildinit.plugins.internal.maven.Maven2Gradle$this$2$generateFqn.callCurrent(Unknown Source)

Any progress on this issue?

Hey Thomas,
I'm working on that and I really thought I solved it. As a reference project I used the netty project. Are you able to create a small selfcontained example that reflects your maven multi project structure? Do you reference external parent poms in your maven multimodule build?

Thanks for the pointer! I can reproduce the stackoverflow with this project and will have a look.

This was quick. Thanks for looking into this. Looking forward to your findings!

It seems that the problem is a common parent which is != the gradle root project but part of the multi module build. In the opendaylight-controller maven build the rootproject (releasepom) references to common-parent which is in opendaylight/commons/parent

Still, I guess it is valid Maven multi-project setup. What is the solution?

No doubt it's valid maven code but that brought in a circular project lookup in the maven2gradle conversion. I've committed a potential fix which should be in the next nightly.

Thanks again for the quick response. With the latest nightly the conversion succeeds. However the compile than fails as some sub-projects POM references plugin 'xtend-maven-plugin' which seems to have no counterpart on the Gradle side. I guess it will be hard for Gradle to support all possible Maven projects out there.