>The larger question is with regards to trunk. It was requested that
>import not be used there and that importing just be the
>defined behavior of specifying a pom in a dependencyManagement section.
I think the import scope should _NOT_ be assumed for pom projects. Pom
projects serve a third p
Sure. I can document this. I have already written the code that accounts
for the circularity problem. Instead of getting the stack overflow or
out of memory error it will throw a ProjectBuildingException and
identify both the failing artifact and the parent. However, I have to
retest this since
