DependencyManagement(bom) & dependencies in test scope can't be removed

[bsaby]

1. Add some dependencies with bom information or repository information
2. Edit starter, remove these dependencies RESULT: The bom or repository information can't be removed while removing related dependencies

Dependencies in test scope have the same issue.

[Eskibear]

It has the same behaviour with STS IDE. Will discuss about it.

[Eskibear]

The remaining of existing xml nodes is not blocking, actually the blocking issue is that when you add some starters, the dependencies in test scope cannot be added. That leads to failure in build. Just as mentioned in https://github.com/spring-projects/sts4/issues/52#issuecomment-386156039

[kdvolder]

@Eskibear Can you elaborate what you mean by this:

when you add some starters, the dependencies in test scope cannot be added

Do you have an example of this to illustrate it perhaps? Because I don't understand.

[Eskibear]

@kdvolder What I meant was the example you mentioned in https://github.com/spring-projects/sts4/issues/52#issuecomment-386156039

If I select RabbitMQ and Cloud Stream on a new project, I get the amqp starter, spring-cloud-stream, spring-cloud-stream-binder-rabbit and spring-cloud-stream-test-support. If you instead only selects RabbitMQ intially; and subsequently add 'Cloud Stream' via edit starters. Then spring-cloud-stream-binder-rabbit and spring-cloud-stream-test-support are not being added.