The larger question is with regards to trunk. It was requested that
scopeimport/scope 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
Hi all,
I wanted to bring up some interesting effects I've come across having
to do with the new import scope. In what I'd call conventional
cases, this feature seems to work just fine. These cases have been
covered in the core integration-tests for mng-3220. Basically, as
long as the
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
