Using dependencyManagement and pom/import

[Kurt Zettel II <kz...@gmail.com>]

Hello,

I am using dependencyManagement and including a pom with with a scope of
import so I can include it's dependencies' versions.  It works as expected
except for two things:

-the versions plugin can't seem to update this dependency.
-the release plugin doesn't accept a new version of this dependency.

Has anybody else ran into this?

I did a little bit of digging and it looks like it is removing the
dependency from the model and replacing it with the nested dependencies in
the DefaultModelBuilder when it resolves the dependencies.  Is this by
design?

Thank you,

Kurt Zettel