project-add-dependency ignore new scope

When you have a bom defined in depmgm that include the dep you're trying to add as a direct dependency, you will get the question: This is a managed resource, would you like to include this version?

When you attempt to add a reference to a managed dependency in a given scope, the new scope is ignored if you say yes to not override the managed version.

Take Arquillian as an example, arquillian-bom is defined in depmgm.

project-add-dependencies org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain::test:pom

Do you like to use managed version? Y

Results in:

org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain:::pom

Resolver is now in Compile scope. Wanted Test scope.