Depency management with poms with exclusions defined

Hello -

I’ve run into the issue defined in this blog post and that the Spring plugin changes.

The summary is that if I include a dependency who’s pom has exclusions defined in any of it dependencies, those exclusions are ignored.

I’m curious why the default behavior for Gradle is to ignore the exclusions in a Maven pom. This seems counter-intuitive, no?